chrismdp / fix-failing-mainA failing main becomes an issue and a buildPublic · Version 1 of 3#3 · chrismdp · 23 Oct 2026, 9:45am · 0.4Latest#2 · chrismdp · 22 Oct 2026, 10:11pm · 0.4#1 · chrismdp · 22 Oct 2026, 8:42pm · 0.4ShowingForkWho may see each partWhere each part runsYAMLChecksNo mistakesGitHub ActionsGitHub: CI, issues and workflowsActions job in CI: report the failure, running none of the codethe runthe failed jobs' logthe open issues[open][none][opened]the issue's numberTriggerA check fails on mainConnectionThe repository, through itsown Actions tokenCode · bring-inBring in the failed jobs' logDataThe failing checks' outputOnly the repository's own people and workflows can change main, so its log is the repository's own textCode · sortSort by rule: is an issue abouta failing main already open?One open issue at a time, so a main that fails on several pushes starts one build, not one eachCode · doAdd this run to the open issueCode · doOpen an issue with the failingoutput, labelled failing-mainOutside actionOpen or comment on an issueAllowCode · doStart a build of the new issueOutside actionStart the build workflowAllowThe build is drawn at awml.io/chrismdp/issue-to-pull-request. It retries, and merges by the same rules as any other buildFlow only+−Fit