Skip to content

[epic] website: merge-ready PRs (coordination, not for agents) #1041

Open

Description

@Danathar

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.

Work packages

Settings owned by this coordination issue

  • GitHub: ruleset "bluefin" requires test, Audit GitHub Actions and wolves-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

  1. added
    epicMulti-issue initiative tracked on the Bluefin planning board
    on Nov 17, 2026
  2. hivecommons-hive commented on Nov 17, 2026

    @hivecommons-hive
    Contributor

    PR #1042 covers this issue: #1042

    The PR body says this is partial/non-closing work (Refs/Part of or 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicMulti-issue initiative tracked on the Bluefin planning boardhive/partially-addressedA merged PR addressed only part of this issue; remainder still actionablestage/010-actionableTriaged; eligible for the hive to pick up

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions