[Feature Request] Too many commits to push
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
When you have lots of commits to push (let's say 100k), GitHub (and maybe many other services) rejects the push.
I'd like for the client to be aware of the number of commits and try to push them let's say 100 at once, that way the push will get accepted by GitHub
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
Start by tracing the client's existing push implementation and how it determines the commits sent to GitHub. Confirm the service's commit limit and define how batches should be handled, then verify that a push containing roughly 100,000 commits succeeds through multiple batches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100