Record that the push mirror does not propagate branch deletions #10

Merged

hannah-vernon merged 1 commit from docs/mirror-deletion-behaviour into dev

2026-09-09 15:59:47 -05:00

hannah-vernon commented

2026-09-09 15:59:46 -05:00

Owner

Observed twice. A merged branch deleted on Forgejo remains on GitHub, so it must be deleted on both. Also records that Forgejo's branch DELETE API leaves the git ref in place, so git ls-remote is the authority rather than the API listing.

Observed twice. A merged branch deleted on Forgejo remains on GitHub, so it must be deleted on both. Also records that Forgejo's branch DELETE API leaves the git ref in place, so `git ls-remote` is the authority rather than the API listing.

hannah-vernon added 1 commit

2026-09-09 15:59:46 -05:00

Record that the push mirror does not propagate branch deletions 3f2382d743

Observed twice: a merged branch deleted on Forgejo stays on GitHub, so
after every release it must be deleted on both remotes.

Also records that Forgejo's branch DELETE API reports success and drops
the branch from its listing while leaving the git ref in place, which is
why the mirror kept pushing four already-deleted branches.  git ls-remote
is the authority, not the API listing.

No version bump; this is maintainer guidance, not plugin behaviour.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>