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
Decide: What merge-and-release Does When the Promotion Is Already Merged and a Release Was Asked #4019
Split from tracker #3958, a CodeRabbit finding on ptr727/ESPHome-NonRoot#404 against the carried merge-and-release "The Procedure". Re-checked against hub main at 42f2155b.
Question: Step 2 finds the promotion state=MERGED and says "Dispatch no release from here, since whoever merged it may have released it already". It then reports and stops. A session invoked with scope release therefore leaves the promotion unreleased when the other merger did not dispatch. What should it do?
Options, recommended first:
Look, then ask (recommended): read the publisher's runs on the merge commit, and report whether a release started. Where none did, ask the maintainer before dispatching. The release request is not silently dropped, and no double dispatch is risked. No work in flight.
Keep stop-and-report: simplest, and it relies on the report being read. No work in flight.
Answered by the maintainer, 2026-11-10: option 1, look, then ask. Where step 2 finds the promotion already merged under a release scope, read the publisher's runs on the merge commit and report whether a release started. Where none did, ask the maintainer before dispatching. This issue now tracks that edit to merge-and-release "The Procedure".
Activity
Skip Carried Verbatim Trees in Rendered Reviewer Configs (#4020)
Promote Develop: Skip Carried Verbatim Trees in Rendered Reviewer Con…
ptr727 commentedon Nov 10, 2026
Answered by the maintainer, 2026-11-10: option 1, look, then ask. Where step 2 finds the promotion already merged under a release scope, read the publisher's runs on the merge commit and report whether a release started. Where none did, ask the maintainer before dispatching. This issue now tracks that edit to
merge-and-release"The Procedure".ptr727 commentedon Nov 10, 2026
Released (2026-11-10): PR #4029 merged into
developat 6a84ead, and its branch and worktree are removed, so this claim holds no files.Backlog burndown claim (attended run 2026-11-10, round 1, group G7). Branch:
burndown/3897-merge-and-release-kit-install. Issues: #3897, #4019.Predicted file set:
.agents/skills/merge-and-release/SKILL.md.github/skills/merge-and-release/SKILL.md.claude-plugin/fleet-skills/skills/merge-and-release/SKILL.md.claude-plugin/fleet-skills/.source-digests/merge-and-releaseNo other group may edit these files while this claim stands. The orchestrator releases it at cleanup.
Install the Updated Host-Safety Kit and Look Before Asking in merge-a…