gemini-cli-extensions / gemini-cli-extensions/conductor
When we update the conductor extension, it should ask and delete/update previous files and install fresh ones
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
This specifically is important for the projects that already have Conductor setup.
E.g. if the content of a guideline is updated in a new version of the Conductor, we need to make sure that's reflected in the projects.
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 files or tests are named. Start by locating the Conductor extension update and installation entry points, then trace how existing project files are handled. Done should include a defined prompt for deleting or updating previous files and ensure updated guideline content is reflected in projects with an existing Conductor setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100