microsoft / microsoft/VFSForGit
Pass --no-progress argument to `git commit-graph` once the option is available
Open
Nobody has claimed this yet.
affects: mount-reliability
platform: linux
platform: macOS
platform: windows
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Once VFS4G picks up the changes for https://github.com/microsoft/git/issues/177 it should start passing in --no-progress when it calls git commit-graph
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
Search the VFSForGit code for the git commit-graph invocation and read the surrounding compatibility logic. Check how availability of microsoft/git#177 is tracked. Done means the invocation passes --no-progress once the option is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100