Repository navigation
The standard still describes landing by auto-merge, which is never armed #2272
Description
The maintainer decided on 2026-11-14 that auto-merge is never armed in btclib-org: an armed pull request merges at a moment nobody reads. The merge is an explicit act after the approval, by whoever approves or by a session on his word. PR btclib-org/ai-agents-process#437 writes this into the agents' process.
The standard still describes landing by auto-merge: section 11 of README.md, the verbatim CONTRIBUTING.md (Landing it), and the REPOSITORY.md of several trees. A contributor reads the old rule.
No workflow in any tree arms auto-merge or merges a pull request, and no open pull request is armed (measured on 2026-11-14, recorded in the body of PR btclib-org/ai-agents-process#437).
Done when
README.mdand the verbatimCONTRIBUTING.mdhere say the merge is explicit and that auto-merge is not armed, and no passage tells a reader to arm it.- The tests that read those passages pass.
- Each tree's
CONTRIBUTING.mdcopy andREPOSITORY.mdare ported.
Whether allow_auto_merge is switched off in the repositories' settings is the maintainer's decision and is not part of this issue.
Activity
fametrano commentedon Nov 14, 2026
Claimed: a session is writing this in
README.md,CONTRIBUTING.mdandREPOSITORY.mdhere, on branchstandard-no-auto-merge. The ports to the other trees follow it.fametrano commentedon Nov 14, 2026
Hold, for the maintainer's decision (asked 2026-11-14, deferred to the morning report), in two parts. First, whether the pull request for this issue and its ports land through the bypass while the verbatim test is red between the two; the session recommends yes. Second, whether
allow_auto_mergeis switched off in the repositories' settings now that auto-merge is never armed; the session recommends yes, as a separate change. The branch is written and reviewed meanwhile; it is opened, not landed.fametrano commentedon Nov 14, 2026
The hold above is answered, both parts, by the maintainer on 2026-11-14: the pull request for this issue and its ports land through the bypass once each has the reviews' ACK and no open thread; and
allow_auto_mergeis switched off in the eighteen repositories, the expected value in this tree's tests changing in the same pull request.The merge is explicit and auto-merge is off (issue #2272)
The merge is explicit and auto-merge is off (issue btclib-org/.github…
The merge is explicit and auto-merge is off (issue btclib-org/.github…
The merge is explicit and auto-merge is off (issue btclib-org/.github…
The merge is explicit and auto-merge is off (issue btclib-org/.github…