Summary
When Partio pushes the checkpoint branch during pre-push, it always shows the same message regardless of whether new data was actually transferred. Users can't tell if their checkpoints are being synced or if it was a no-op.
What to implement
Parse the output of git push for the checkpoint branch and show distinct messages:
[partio] Pushing partio/checkpoints/v1… done — when new checkpoints were pushed[partio] Pushing partio/checkpoints/v1… already up-to-date — when nothing new to push
Context
internal/hooks/prepush.go — pre-push hook implementationinternal/git/push_branch.go — PushBranch() function
Why
Users who push frequently see identical messages every time and can't tell if checkpoint data is actually flowing. This is especially confusing when debugging checkpoint remote issues.
Inspired by: entireio/cli#927
Summary
When Partio pushes the checkpoint branch during
pre-push, it always shows the same message regardless of whether new data was actually transferred. Users can't tell if their checkpoints are being synced or if it was a no-op.What to implement
Parse the output of
git pushfor the checkpoint branch and show distinct messages:[partio] Pushing partio/checkpoints/v1… done— when new checkpoints were pushed[partio] Pushing partio/checkpoints/v1… already up-to-date— when nothing new to pushContext
internal/hooks/prepush.go— pre-push hook implementationinternal/git/push_branch.go—PushBranch()functionWhy
Users who push frequently see identical messages every time and can't tell if checkpoint data is actually flowing. This is especially confusing when debugging checkpoint remote issues.
Inspired by: entireio/cli#927