cproudlock 06c584240e Mirror the publication branch BEFORE the sync, not after ...

The branch checkout landed after the rsync, where git checkout --force reverts
the tree to the branch's committed state and discards everything rsync had just
written. The export then found no changes and published nothing, while still
printing a bundle path and looking like it had worked. A silent no-op is the
worst shape for this: the next person believes the export ran.

Scope: product

2026-08-30 09:04:56 -04:00

13 KiB

Executable File

Raw Blame History

View Raw