Limits the number of max commits
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
Sometimes, commits are periodically produced by batch applications. In that case, the commit history of the repository is extremely huge.
For example, the number of commits of one of the biggest repositories is bigger than 130k.
The big history impacts disk usage. And it is also bad for performance because it can cause slow queries.
It would be nice if we can limit and configure the maximum allowed number of commits for a repository. If a repository exceeds the max history, old commits would be truncated.
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 by locating how Central Dogma stores and queries repository commit history, then find where repository-level settings are defined and validated. Determine how a configurable maximum and safe truncation of old commits would interact with existing history queries and persistence; done means the behavior is specified and covered for repositories above the limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100