gemini-cli-extensions / gemini-cli-extensions/conductor
Inconsistent handling of completed tracks
Open
Nobody has claimed this yet.
area:implement
bug
p1
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
I have observed that Conductor's handling of completed tracks is inconsistent, even within a single workspace.
For example, I have observed the following actions when a track is closed:
- The track may or may not be moved to a new
conductor/archivesfolder. - The track may be marked as complete with
[x]intracks.md, or it may be deleted fromtracks.mdcompletely.
The workflow.md currently contains no explicit steps as to what should happen when a track is closed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with workflow.md, tracks.md, and the conductor/archives path mentioned in the report. Determine and document one consistent outcome for archiving closed tracks and representing them in tracks.md. Done means workflow.md explicitly states the steps for closing a track.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100