Squash Git History for sqlite Branch
Open
Nobody has claimed this yet.
database
P1
- Dominant language
- JavaScript
- Stars
- 61
- Forks
- 21
- Avg merge
- 26d 5h
- Merged PRs (30d)
- 1
Description
To prevent an explosion of storage usage by the sqlite branch, we need to squash this history every commit we push. Maybe, worst case, we keep a .backup copy of the previous commit each time.
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 reviewing the sqlite branch history and the workflow used to push commits to it. Define how history should be squashed and whether a previous commit backup is required; the work is done when the branch no longer grows storage through unsquashed commit history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, sqlite
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100