gemini-cli-extensions / gemini-cli-extensions/conductor
how to: conductor plugin for development of micro-services where each service is in its own repo
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
This is not an issue per se - I'm using claude code and I'm trying to understand how best to use this conductor plugin for development of micro-services where each service is in its own repo:
- where a single conductor project will be across a few of these micro-service repos'.
- I was expecting that the conductor planning and whole process would be conducted in a single repo for the purpose of maintaining context
- maybe even using a repo precisely for conductor to hold all its plans irrespective of which of the micro-service repos' was getting coded.
Any advice on this will be sincerely appreciated.
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
No file, test, or entry point is identified in the report. First clarify whether the requested outcome is usage advice or documentation for multi-repository workflows; done means the supported way to maintain plans and context across service repositories is stated clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100