Skip to content

docs: capture the dependabot gate friction, rule the route, and plan the bounded re-authoring - #660

Merged
REPPL merged 2 commits into
mainfrom
chore/capture-dependabot-gate
Sep 22, 2026
Merged

REPPL merged 2 commits into
mainfrom
chore/capture-dependabot-gate

Conversation

@REPPL

@REPPL REPPL commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

What

  • iss-2609221820487644: the attribution gate blocks every bot-opened dependency bump, and the request to change that. The record names the mechanism precisely, because the request named the trailer and the trailer is not what fails: the gate refuses a bot on identity, on two independent signals, and deliberately stays silent about a missing Assisted-by so the remedy is not misread. It lists three candidate shapes and says the change needs a decision, since it touches a stated rule.
  • The ruling, recorded on that record: route 2. A workflow re-authors a bot-opened bump as the repository owner before the gate runs; the gate itself does not change.
  • itd-2609221842494980, planned and READY: the bounded re-authoring. A commit is re-authored only when its branch is one the forge marks as a declared bot's and its diff touches nothing but that ecosystem's manifest and lock file, across every ecosystem dependabot opens rather than Go alone; anything else is left untouched with the failing clause named. The message names the bot and the workflow and carries Assisted-by: None. The attribution script is not edited, and a test asserts it still refuses the bot's original while passing the re-authored commit. Scaffolded into a managed repository by the same verb that writes its release workflows, opt-in.

Why

The gate's consequence is deliberate and written down. Its cost was not: every bump sits with auto-merge armed and every other check green, in a blocked state that reads as a missing review, and the only way through is a person re-authoring a two-line diff. One did that tonight, at the price of a hand-authored branch and two full gate runs.

A point named rather than assumed

A workflow that re-authors asserts the repository owner's authorship with no person in the loop. That is a different claim from a commit a person asked for, even though the gate would pass either. The record says so, and the owner's acceptance is made once in the configuration, under the diff-shaped bound.

Records

Refs: iss-2609221820487644

Assisted-by: Claude:claude-opus-5

…bution gate

The product thinker asked for the gate to change after PR 655 sat blocked
with auto-merge armed. The record names the mechanism precisely, because
the request names the trailer and the trailer is not what fails: the gate
refuses a bot on identity, and the script deliberately says nothing about
a missing trailer so the remedy is not misread. It reverses a stated rule,
so the record asks for an ADR and a brief invariant before any code moves,
and lists three candidate shapes for that decision to weigh.

Refs: iss-2609221820487644
Assisted-by: Claude:claude-opus-5
…record the ruling that chose it

Route 2 of the three the capture named: a workflow re-authors a bot-opened
bump as the repository owner before the gate runs, bounded by the diff's
shape (an ecosystem's manifest and its lock file on a branch the forge
marks as that bot's) across every ecosystem dependabot opens, with the
message naming the bot and the workflow and carrying Assisted-by: None.
The attribution gate is not edited. Scaffolded into a managed repository
by the verb that writes its release workflows, opt-in. The authorship
point is named on the record rather than assumed.

Refs: iss-2609221820487644
Assisted-by: Claude:claude-opus-5
@REPPL
REPPL enabled auto-merge September 22, 2026 18:50
@REPPL
REPPL added this pull request to the merge queue Sep 22, 2026
Merged via the queue into main with commit df31264 Sep 22, 2026
12 checks passed
@REPPL
REPPL deleted the chore/capture-dependabot-gate branch September 22, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant