GitTools / GitTools/GitVersion
Commit-graph accelerator for the managed reader (Phase F, optional)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.1k
- Forks
- 659
- Avg merge
- 13h 15m
- Merged PRs (30d)
- 51
Description
Optional performance work: read .git/objects/info/commit-graph and use generation numbers to accelerate topological sorting and merge-base computation; benchmark-driven (BenchmarkDotNet end-to-end and revwalk/merge-base micro benchmarks).
Part of #5031 — see docs/design/managed-git-migration.md for the full design.
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 with docs/design/managed-git-migration.md to understand the managed reader design and how this Phase F work fits. Then inspect the BenchmarkDotNet end-to-end benchmark and the revwalk/merge-base micro benchmarks. Done means the commit-graph and generation-number approach is implemented and the named benchmarks demonstrate its performance impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100