Pre-push checkpoint sync shows no progress during long pushes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 178
Description
Problem
When git push triggers Entire's pre-push hook, checkpoint sync can take a long time (fetch, cherry-pick rebase onto remote tip, retry push, OPF). Users only see:
[entire] Pushing entire/checkpoints/v1 to origin...
.....
There is no indication of which phase is running (fetching, rebasing commit 3/12, transfer progress, etc.), so pushes feel stuck.
Expected
Structured stderr progress aligned with Story CLI: session summary before push, git transfer phases, sync/rebase step labels with elapsed time.
Notes
Failures remain non-blocking for the user's main push (except OPF privacy aborts); this is display-only.
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 tracing the pre-push hook's checkpoint sync path and comparing its stderr output with the Story CLI progress format. Done means users see a session summary, labeled Git transfer and sync/rebase phases, commit progress, and elapsed time while preserving the stated non-blocking failure behavior and OPF privacy abort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100