conflict gitignore entries issue
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
For example, .gitignore contains:
temp.txt
!abc/**
Then we have abc/temp.txt, in git status it will show clean, while git2 will show it as Untracked files abc/temp.txt.
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 by reproducing the .gitignore example with temp.txt, !abc/**, and abc/temp.txt, then compare git status with git2's untracked-file result. Done means git2 handles this ignore conflict consistently with git status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100