Depends on every gate leg landing first. This is deliberately last in the
milestone: requiring a check that does not exist yet blocks all work, and
requiring a check that has never refused anything gives false comfort.
Today nothing is required:
gh api repos/Flowfin/hub/rules/branches/main --jq '[.[].type]'
["deletion","non_fast_forward","pull_request"]
Run 2026-08-07. So every workflow this board carries is advisory, and a pull
request with every check red can be merged.
What this issue changes is a repository setting rather than a file, which is
worth saying because it is the one part of this plan that leaves no diff. The
change should therefore be recorded with the command that shows the result, so
that a later reader can tell what the gate was on a given day without trusting a
document.
Three things to settle while making the change. Which check names are required,
taken from what the workflows actually produce rather than from what anybody
remembers. Whether bypass actors exist, and the honest default is none, including
for the person making the change. And whether signed commits are required, which
the target board does not require today and which is worth deciding on its own
merits rather than by copying.
Done when
The ruleset lists the required check names, the bypass list is empty or its
contents are justified in the issue, and the issue body carries the command and
output showing the final state. Machine-decidable.
Depends on every gate leg landing first. This is deliberately last in the
milestone: requiring a check that does not exist yet blocks all work, and
requiring a check that has never refused anything gives false comfort.
Today nothing is required:
Run 2026-08-07. So every workflow this board carries is advisory, and a pull
request with every check red can be merged.
What this issue changes is a repository setting rather than a file, which is
worth saying because it is the one part of this plan that leaves no diff. The
change should therefore be recorded with the command that shows the result, so
that a later reader can tell what the gate was on a given day without trusting a
document.
Three things to settle while making the change. Which check names are required,
taken from what the workflows actually produce rather than from what anybody
remembers. Whether bypass actors exist, and the honest default is none, including
for the person making the change. And whether signed commits are required, which
the target board does not require today and which is worth deciding on its own
merits rather than by copying.
Done when
The ruleset lists the required check names, the bypass list is empty or its
contents are justified in the issue, and the issue body carries the command and
output showing the final state. Machine-decidable.