libgit2 / libgit2/libgit2sharp
Fetch on Bare are Not Only Changes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Recently, I discovered that when I fetch a bare local repo, I often fetch a large number of git objects from remote to local (if there has some changed). However, most of the fetched objects already exist on the local side (not only changes).
This will cause my bare repo size to increase The bigger it is, the more time will be wasted waiting for network transmission
Expected behavior
Fetch only changes objects.
Actual behavior
Fetch a lot of object even it's already exists on the local repo.
0.26.2
Operating system(s) tested;
Windows11, NetFrameWork 4.7.2
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
The issue does not name a source file, test, or entry point. Reproduce a bare local-repository fetch on Windows 11 with .NET Framework 4.7.2 and version 0.26.2, comparing transferred objects with objects already present; done when only missing objects are fetched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100