create .gitignore file whenever the conductor extension initialize the git in a workspace
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git
- Domain
- tooling
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.
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.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 297
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day