gemini-cli-extensions / gemini-cli-extensions/conductor
create .gitignore file whenever the conductor extension initialize the git in a workspace
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
I was working on a new project and started with a fresh workspace. Conductor initialized git, and then installed npm packages and committed each change, including adding everything in node_modules to the git history.
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 at the conductor extension's workspace git-initialization flow and trace when npm packages are installed and committed. Ensure a .gitignore is created before those commits so node_modules is not added to the git history; verify this with a fresh workspace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100