From a65556726e7b5519956b39bfbb26ec9a7862056a Mon Sep 17 00:00:00 2001 From: Silent Mode Date: Mon, 21 Sep 2026 03:23:14 +0200 Subject: [PATCH] docs(sirius-press): say that the forge repo is a mirror, and what that costs Someone who clones from code.silentmode.st and starts working will otherwise find out the hard way: push-split.sh force-pushes master, so their branch does not survive the next mirror push. Better to say it on the page that tells people how to take an upstream release, since that is exactly the work that would be lost. --- docs/upstream-merges.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/upstream-merges.md b/docs/upstream-merges.md index 264df83..856626b 100644 --- a/docs/upstream-merges.md +++ b/docs/upstream-merges.md @@ -121,6 +121,28 @@ replaced from plugins precisely so they would never appear in this directory. --- +## Where this repository lives + +`code.silentmode.st/silentmode/sirius-press` is a **mirror**. Sirius Press is +developed inside the Silent Mode monorepo and split out with +`scripts/push-split.sh`, which force-pushes `master` each time. History on the +forge is real — file blame points at the actual commits — but it is rewritten +on every push, so a pull request against it will not survive. + +What that means in practice: + +- **Silent Mode takes upstream releases in the monorepo**, where the subtree's + merge history is intact, and the result is mirrored here. +- **A downstream fork** that clones from the forge and wants to bump WordPress + itself should treat its clone as the source of truth from that point on and + stop pulling the mirror, because the next mirror push will not merge with + its work. + +Patches and bug reports are welcome as issues; code is easiest to take as a +diff rather than as a branch. + +--- + ## If the upstream branch is missing A clone made with `--single-branch` will not have