Repository navigation
Phase 2: nothing checks a pull request #191
Description
Activity
All six items landed with #193, and the boxes above are ticked.
The protection on
editionis now set, which is the half that code cannot express. Until today the checks ran on every pull request but blocked nothing: one approving review was enough to merge with all three of them red.What is required now:
Setting State Approving reviews required 1 Required status checks Build the site, Check the content, Check the links Code owner review required yes Enforced on administrators no The link check reports without failing, so a rate-limited external site does not block a merge. The rule is not enforced on administrators, so an organizer can still unblock the repository if something goes wrong with the checks themselves.
A branch protection setting lives only in the repository settings: it is in no file, appears in no diff, and nothing records who changed it or why. This comment is its history, which is why it is here and not in a pull request.
Closing.
Approved by the Permanent Committee on 2026-09-30. This is the issue that explains why #190 exists.
A pull request to this repository runs no checks at all. Not a build, not a link check, nothing. Every item in #190 landed and stayed because nothing looked.
idmatches its filename, ids are unique, declared photos exist, and every person and sponsor id an event references resolves. This finds 6 errors on the current content, two of them visible on the live siteactions/checkout@v3is four majors behind and runs on a deprecated Node runtime, the other two are one major each, and the runner image is deprecatedOrdering: the content check cannot go green until the phase 1 fixes land, so these arrive in that order.