Pushing a new bookmark sends the whole history, not what the remote lacks issue #142 closed: completed andymccall opened this 10 days ago · 0 comments

Found 2026-10-25 pushing oxygenhub's draft-ready bookmark (oxygenhub#313): push protection refused it for AWS's documented example key in an old version of backups.rs, a change main has had for weeks. push_bookmark_with negotiates against the remote's heads for that bookmark only (negotiate(&remote_heads, &local_heads)), and a new bookmark has none, so every change of its history is sent again: slow for a big repository, and the hub's push protection scans all of it.

Fix: what the remote lists under every bookmark, of the changes held here, counts as already there; a new bookmark made from main sends only the changes main lacks.