Make staging / batch commits more easily accessible
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Smart idea from @ryv-odoo: expose as a git repository using submodules, this should be reasonably easy to generate, as it's only hashes there isn't really anything to compress, so we can create a naive packfile.
Submodules are not great, but they should be good enough for this use case.
- migration to create commits (somewhat efficiently) for all old stagings / batches
- creation of commits for stagings
- async?
- actually push to repository
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 existing creation of commits for stagings described in the checklist, then determine how old stagings and batches should be migrated into a repository exposed through submodules. Implement the remaining migration and repository-push work, and verify that historical stagings and batches are accessible as commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100