feature request: way to separate conductor metadata commits from conductor output
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- markdown
- Domain
- tooling
Research direction
Start by reviewing the markdown files that instruct Conductor how to commit and track work, then trace how a track currently commits generated code and files in the conductor directory. Determine a reliable workflow that places track output in one change and conductor state updates in an immediate follow-on change; done means those artifacts are consistently separated.
Written by the indexing model from the issue text.
Description
I often find that conductor will commit updates to the files in the "conductor" directory in the same CL as the code that it generates as part of the track it's executing. My ideal work flow would be to commit only the output of the track in one change, and then in an immediate follow on CL commit modifications to the conductor state files. This simplifies the process of code review and separates the artifacts that are generated from the artifacts used to track progress.
I have attempted to do this by modifying some of the md files that instruct conductor how to commit and track work. I have had some limited success but have yet to arrive at a reliable way to separate the code generated by a track from the track management.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Getting set up
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.
More from gemini-cli-extensions/conductor
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gemini-cli-extensions/conductor#176 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gemini-cli-extensions/conductor#72 · 1 reaction ·
-
how to: conductor plugin for development of micro-services where each service is in its own repoOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
gemini-cli-extensions/conductor#168 · 4 comments ·
All issues in gemini-cli-extensions/conductor
Similar issues
-
pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8843 ·
Maintainers usually reply within 1 day
-
breaking change enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sktime/sktime#11310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day