The swarm section now says what each branch is for: the landing branch ships and moves only when a person approves a publish; the pilot branch is where reviewed PR branches come together; each plugin or feature has its own PR branch. A new paragraph says how it scales (many people, each with several agents, on many plugins: one PR branch each, seen on the pilot server once it joins). Step 5 names the lock as a merge queue. Publishing to a public host happens only from the landing branch, when it is ready, and a self-hosted git service is recommended because an agent can publish by accident. The diagram gets the same: "a person approves" for the landing, "landing server", and a bottom band for the scale and publishing rules. The PNG is re-rendered at 2x from the SVG source.
926 KiB
3000x4512px
926 KiB
3000x4512px