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
One comment per confirmed red full run on main: the culprit post-merge-demotion-alert.yml's report job pinned, the evidence runs, and the revert it would open. docs/conventions/pr-pipeline/README.md, "Red main", states the rule. The job writes nothing else while red-main.dry-run is true.
No culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (e649d303f4a6) by dispatching pr-require-checks on a branch at that commit.
No revert pull request: a person picks the merge from the post-merge record.
No culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (07ffa9c3bb17, dd8cb318b461, eb4beb8000f9) by dispatching pr-require-checks on a branch at that commit.
No revert pull request: a person picks the merge from the post-merge record.
No culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (33afb115c9e3, 74bee5d9bec7, 7425e6f170c5, 95af3ee53bd0, 98c3a04f37c6, b026b85af8ba, 270a99643677, 11254a8ddeb7, cd51d31f5629, d31b0c6333c6) by dispatching pr-require-checks on a branch at that commit.
No revert pull request: the fix issues fix main forward.
Closing: this log works as a closed issue. post-merge-demotion-alert.yml's red-main report job (.github/scripts/post-merge-demotion-alert/report.mjs) finds it as the oldest github-actions issue carrying <!-- red-main-revert-log --> in any state (report.mjs:159, state=all), adds one comment per confirmed red, and has no reopen path. Its dedup and revert cap read these comments (report.mjs:170), whatever the issue's state. Reports keep landing here as comments and in each run's step summary. Owner order 2026-11-07: get to 0 open issues.
Activity
github-actions commentedon Oct 22, 2026
Red main at
ba598f08d306: no culpritMode: dry-run; nothing was pushed, opened or merged.
test-bash (1)0174bdf6410395ffcfd7989cb805bf18b930176f(https://github.com/melodic-software/claude-code-plugins/actions/runs/39847252887)e649d303f4a6ba598f08d306No culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (
e649d303f4a6) by dispatching pr-require-checks on a branch at that commit.No revert pull request: a person picks the merge from the post-merge record.
github-actions commentedon Oct 30, 2026
Red main at
abaf7762e4a1: no culpritMode: dry-run; nothing was pushed, opened or merged.
test-node3ec5bf282707be8bce7d34d60b3d3b30e0d0b4ef(https://github.com/melodic-software/claude-code-plugins/actions/runs/41000543542)07ffa9c3bb17dd8cb318b461eb4beb8000f9abaf7762e4a1No culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (
07ffa9c3bb17,dd8cb318b461,eb4beb8000f9) by dispatching pr-require-checks on a branch at that commit.No revert pull request: a person picks the merge from the post-merge record.
github-actions commentedon Nov 4, 2026
Red main at
4c0b4eb3855c: no culpritMode: dry-run; nothing was pushed, opened or merged.
test-bash (3),test-bash (3): lib/view-settings.test.sh8f87fee5bcffeff1fc44bd51b23792981060aa63(https://github.com/melodic-software/claude-code-plugins/actions/runs/41785637581)33afb115c9e374bee5d9bec77425e6f170c595af3ee53bd098c3a04f37c6b026b85af8ba270a9964367711254a8ddeb7cd51d31f5629d31b0c6333c64c0b4eb3855cNo culprit: no merge in the range fails where its parent passes on the evidence runs.
To pin one, the bot would run the full suite at each untested merge (
33afb115c9e3,74bee5d9bec7,7425e6f170c5,95af3ee53bd0,98c3a04f37c6,b026b85af8ba,270a99643677,11254a8ddeb7,cd51d31f5629,d31b0c6333c6) by dispatching pr-require-checks on a branch at that commit.No revert pull request: the fix issues fix main forward.
github-actions commentedon Nov 6, 2026
Red main at
50dc172d6246: fixed forward, no revertMode: dry-run; nothing was pushed, opened or merged.
test-noded23b140ab6668843aef46e8e12390464864827b4(https://github.com/melodic-software/claude-code-plugins/actions/runs/42146042896)50dc172d6246Culprit:
50dc172d6246c4985df27f89658a31017aa99d7d(#13632), merged 2026-11-06T02:04:51Z, fails where its parent passes.No revert, because:
The fix issues fix main forward.
kyle-sexton commentedon Nov 7, 2026
Closing: this log works as a closed issue. post-merge-demotion-alert.yml's red-main report job (.github/scripts/post-merge-demotion-alert/report.mjs) finds it as the oldest github-actions issue carrying
<!-- red-main-revert-log -->in any state (report.mjs:159,state=all), adds one comment per confirmed red, and has no reopen path. Its dedup and revert cap read these comments (report.mjs:170), whatever the issue's state. Reports keep landing here as comments and in each run's step summary. Owner order 2026-11-07: get to 0 open issues.session: automation-lanes