Multiplayer agent harness for work.
Seed a private fork by pushing main alone (#1160)
Kristofer Sommestad30445f28ea4e
diff --git a/.codex/skills/update-qm/SKILL.md b/.codex/skills/update-qm/SKILL.mdindex 6238e2a05..f8fc4d018 100644--- a/.codex/skills/update-qm/SKILL.md+++ b/.codex/skills/update-qm/SKILL.md@@ -122,9 +122,10 @@ fork never received will fail until those are supplied.## Never do these-- `git push --mirror` to an existing private fork. It deletes refs the destination has and the- source does not, discarding the organization's own branches. It is safe only for the- first population of an empty repository.+- `git push --mirror` to a private fork. It deletes refs the destination has and the+ source does not, discarding the organization's own branches, and into an empty+ repository it copies every upstream branch, leaving GitHub to pick the default among+ them. Seed a fork by pushing `main` alone, as the README shows.- Pushing a branch whose history contains organization commits to upstream. The`upstream-pr` skill pushes upstream only from branches cut fresh from `upstream/main`and scrubbed.diff --git a/README.md b/README.mdindex 15e8ce227..ff5daea7a 100644--- a/README.md+++ b/README.md@@ -174,7 +174,7 @@ Populate it once, then clone it to work in:gh repo create <org>/qm-private --privategit clone --bare [email protected]:yc-software/qm qm-seed.git-git -C qm-seed.git push --mirror [email protected]:<org>/qm-private+git -C qm-seed.git push [email protected]:<org>/qm-private mainrm -rf qm-seed.gitgit clone [email protected]:<org>/qm-private@@ -192,6 +192,11 @@ these problems, and it costs one thing: the clone is an ordinary repository, soCI workflows run live in your own account. Expect to supply the secrets those workflowsneed, or disable the ones you do not want running.+Push `main` alone. A `--mirror` push copies every upstream branch and tag into the empty+repository, and GitHub then makes the alphabetically first branch the default, so pull+requests, clones, and tooling land on a stale feature branch instead of `main`. The+`update-qm` skill fetches everything else it needs from the `upstream` remote.+Everything specific to your organization goes in `deploy/layers/<org>/` — config, sandboxtools and skills, plugin images, infrastructure — in the same shape `qm init` produces. See[`deploy/layers/README.md`](./deploy/layers/README.md). Core stays byte-identical to