Follow-up from #60.
hooks.d/after_save/50-git-backup.sh calls git push with no explicit remote or branch — it relies on the tracking branch configuration. This is fine for the standard origin main setup, but brittle for users with multiple remotes or non-standard tracking configs (they could end up pushing memory to the wrong place).
Proposal options:
- Document the assumption clearly in the README setup section
- Or make remote/branch configurable (
git_backup.remote, git_backup.branch)
- Or detect ambiguous tracking and skip the push with a logged warning
Lowest-effort path is probably documentation + a git symbolic-ref check that logs which remote/branch is being used on first commit.
Follow-up from #60.
hooks.d/after_save/50-git-backup.shcallsgit pushwith no explicit remote or branch — it relies on the tracking branch configuration. This is fine for the standardorigin mainsetup, but brittle for users with multiple remotes or non-standard tracking configs (they could end up pushing memory to the wrong place).Proposal options:
git_backup.remote,git_backup.branch)Lowest-effort path is probably documentation + a
git symbolic-refcheck that logs which remote/branch is being used on first commit.