docs: swarm-builder merge gate wording in the active voice
This commit is contained in:
parent
5814f177c8
commit
627e07cf82
1 changed files with 3 additions and 3 deletions
|
|
@ -122,7 +122,7 @@ status has no link.
|
|||
host's store until it's collected, so on a host that also runs the hive, the
|
||||
hive's own build can reuse whatever matches. A [meta build](#deploy-gate)
|
||||
can push to [a binary cache](#binary-cache).
|
||||
- The PR check gates the merge: `swarm-builder` is a required status on every
|
||||
- The PR check gates the merge: `swarm-builder` is a mandatory status on every
|
||||
config repo's `main`, so a red or missing status blocks it. The
|
||||
[deploy gate](#deploy-gate) is a separate build, from `internal/meta`.
|
||||
- A lost webhook delivery of a PR push isn't retried: the head isn't built until the next
|
||||
|
|
@ -714,7 +714,7 @@ newer push replaces its PR's job while that job is still waiting. The builder
|
|||
builds that config at the PR's head on the agent base its own host runs,
|
||||
through the host's nix daemon, and swarm-controller writes the result as a `swarm-builder`
|
||||
commit status on the head. The job shows on the swarm UI's Jobs page. The
|
||||
status is required on `main`: a red or missing one blocks the merge.
|
||||
status must pass before a merge to `main`: a red or missing one blocks it.
|
||||
|
||||
Separately, the builder builds each agent from `internal/meta` before the swarm
|
||||
sends its deploy, and a failed or unpushed build holds that deploy back (`build_meta` job;
|
||||
|
|
|
|||
Loading…
Reference in a new issue