CommandCodeAI / CommandCodeAI/command-code
can we have .cmdignore? like .gitignore?
Open
Nobody has claimed this yet.
p2
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
so that .env files aren't being red by
Actual Behavior
so that .env files aren't being red by
Command Code Version
Microsoft Windows(c) Microsoft Corporation. All rights reserved.>
Operating System
Windows
Terminal/IDE
vscode
Shell
git bash
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
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
The issue names no implementation files, tests, or entry points. Start by locating the CLI's existing file-reading and ignore handling, then clarify what “.env files aren't being red” means; done should include a defined .cmdignore behavior that prevents the intended files from being read and tests for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100