You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Session Handoff [auto-2412]: Add Proof Items for the Merge-Bot rules Input and merge-app Job (#2412) #2663
Fix Add Proof Items for the Merge-Bot rules Input and merge-app Job #2412. docs/reusable-workflows.md "What a Pilot Proves" names four merge-bot proofs the hub cannot make itself, and only two of them have a Proof: checkbox, under "Stage 1: Merge-Bot Adoption". Add a Proof: item for the rules input end to end and one for the merge-app job. Each item names a repository that can produce the proof, chosen from the rollout list and the registry rather than guessed. The issue's own test is a repository whose stub sets rules for the first, and a repository whose App opens pull requests for the second. The homeassistant-purpleair row in Stage 1 already carries a rules value, so check it for both before looking further. Update the "What a Pilot Proves" sentence that says Add Proof Items for the Merge-Bot rules Input and merge-app Job #2412 tracks the other two, and the matching TODO.md detail, so neither points at an issue that no longer tracks them. Done looks like a feature -> develop pull request carrying Closes on promotion: #2412, merged, with the prose gate clean on the changed lines, and promoted as far as the run's scope allows.
External blockers
None.
Internal dependencies
None. The lane holds the one issue.
State
No branch, worktree, or pull request exists for this lane yet.
Filed along the way:Tick Merge-Bot Stage 1 Items the Live Evidence Already Closes #2664 (pre-existing), for the Stage 1 items the live evidence already closes: the homeassistant-purpleair adoption row, and the two PhotoCleaner proof items whose behavior other adopters have already shown.
Next steps, in priority order
docs/reusable-workflows.md"What a Pilot Proves" names four merge-bot proofs the hub cannot make itself, and only two of them have aProof:checkbox, under "Stage 1: Merge-Bot Adoption". Add aProof:item for therulesinput end to end and one for themerge-appjob. Each item names a repository that can produce the proof, chosen from the rollout list and the registry rather than guessed. The issue's own test is a repository whose stub setsrulesfor the first, and a repository whose App opens pull requests for the second. The homeassistant-purpleair row in Stage 1 already carries arulesvalue, so check it for both before looking further. Update the "What a Pilot Proves" sentence that says Add Proof Items for the Merge-Bot rules Input and merge-app Job #2412 tracks the other two, and the matchingTODO.mddetail, so neither points at an issue that no longer tracks them. Done looks like a feature -> develop pull request carryingCloses on promotion: #2412, merged, with the prose gate clean on the changed lines, and promoted as far as the run's scope allows.External blockers
None.
Internal dependencies
None. The lane holds the one issue.
State
origin/developandorigin/mainpointed at the same commit, and the only open pull request was Stop Calling Closed Issues #699 and #700 Open in fleet-map.md #2661, which belongs to another lane.The parked decision queue
Zero parked decisions on this lane.
What the last round did
The unattended picker ranked the open backlog and created this lane for #2412. The issue states one determined fix and carries no comment.
What not to repeat
Nothing yet.
New learnings
None.