Disabling altogether on individual slow repositories
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.8k
- Forks
- 134
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Description
I use gitstatus with Windows Subsystem for Linux, where accessing Windows disks is pretty slow. I have a couple of repositories still on Windows disks as I need them accessible to native Windows tools, which means my bash prompt can slow to 10 seconds or more evaluating the git status.
I've set the options mentioned in https://github.com/romkatv/gitstatus/issues/231#issuecomment-821024952:
git config --local bash.showUntrackedFiles false
git config --local bash.showDirtyState false
...which reduces the wait to about 3-4 seconds on a particularly large repository, but that's still pretty painful for interacting with it.
Can I opt-out one or more repository paths completely though config, or do I need to get my hands dirty making the bash prompt conditional on $PWD or similar?
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
No file or test is named. Start at the bash prompt's handling of the existing local options bash.showUntrackedFiles and bash.showDirtyState, then trace how repository paths are evaluated. Done means a repository can be completely excluded from status evaluation through configuration, with the prompt remaining responsive there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, cpp
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100