Repository navigation
Description
What this is, in plain words: Danathar opened this on 2026-11-17. The aim is to make website pull requests quick and safe for you to merge. Nothing merges here without a person, and that stays the same.
- What changed: a pull request can no longer be merged while its tests are failing. Before, GitHub would let an approved pull request through even if the tests were red. (Technically: the "bluefin" ruleset now requires three checks to pass.)
- What we're asking of you: approve pull request ci: open an issue when CI or the Pages deploy fails on main #1042 when you have a minute. It adds an automatic warning when the site's tests or publishing break.
- To undo: in Settings → Rules → "bluefin", remove "Require status checks to pass".
- Questions: ask Danathar.
What this tracks
Maintainer-requested tracking for making website PRs as easy as possible for a person to merge, using the parts of the automation baseline that don't depend on the hive merging. The hive's auto-merge stays off here (the owners' decision); a person still approves and merges every PR. This is a coordination issue: it holds no work of its own, and agents and contributors should not pick it up.
The goal: every PR the hive marks stage/090-ready-for-human-merge is green, current and explained, so a maintainer only has to approve and merge.
Evidence and scope
Checked live on 2026-11-17 at website main f8562fc, against the hive running 3b50113.
- Already in place:
- merge queue (ruleset "bluefin" 2647761: merge commits, 60 minutes) with 1 required approval;
ci.ymlruns onmerge_group; - the hive reviews and labels PRs: chore(deps): update dependency playwright to v1.65.1 #1034–fix(deps): update dependency js-yaml to v5 #1037 (Renovate) reached
stage/090-ready-for-human-mergegreen and approved; - Renovate waits 3 days, merges only pin updates on its own, and rebases PRs when
mainmoves; - issues from members and collaborators are worked without a label.
- merge queue (ruleset "bluefin" 2647761: merge commits, 60 minutes) with 1 required approval;
- Gaps:
- no required status checks: the ruleset requires an approval but no checks, so GitHub and the queue would merge a red PR, and a person has to read the checks by hand.
ci.yml'stest(lint, typecheck, unit tests, full build),Audit GitHub Actionsandwolves-movie-flowrun on every PR and in the queue, and have passed on everymainrun since 2026-11-16; - nothing files an issue when
CIorDeploy to GitHub Pagesfails onmain(both have been green onmaintoday; this is so a future failure is caught without someone watching); - Renovate's npm (12) doesn't match CI's (Node 26, npm 11), so lockfile updates fail (renovate: pin Renovate's npm to 11 so lockfile updates work again #1031; the hive's fix is fix(renovate): keep the dependency-update bot on the same installer version as our checks #1040).
- no required status checks: the ruleset requires an approval but no checks, so GitHub and the queue would merge a red PR, and a person has to read the checks by hand.
Work packages
- fix(renovate): keep the dependency-update bot on the same installer version as our checks #1040 (hive): pin Renovate's npm to 11 so lockfile updates work again (fixes renovate: pin Renovate's npm to 11 so lockfile updates work again #1031).
-
ci-alert.ymlforCIandDeploy to GitHub Pagesonmain(the dakota-iso version ateb13d01). PR ci: open an issue when CI or the Pages deploy fails on main #1042; needs an approval from a maintainer other than its author.
Settings owned by this coordination issue
- GitHub: ruleset "bluefin" requires
test,Audit GitHub Actionsandwolves-movie-flow(2026-11-17 3:55 PM EST, Danathar's OK as maintainer). - Repo docs written once the rest is done, including every human touch.
Not changing
- The hive's auto-merge (off), the required approval, the merge method and queue settings, fork-PR approval, and the Renovate policy. These are the owners' choices.
Decision boundary
Danathar (maintainer) approved this direction on 2026-11-17, with auto-merge staying off. Close this when every box is ticked.
Activity
hivecommons-hive commentedon Nov 17, 2026
PR #1042 covers this issue: #1042
The PR body says this is partial/non-closing work (
Refs/Part ofor leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.