awml
Sign in

chrismdp / systems / factory

The AWML factory

System · Public ·
Version 2 of 4
  1. #4 · chrismdp · Latest
  2. #3 · chrismdp ·
  3. #2 · chrismdp · Showing
  4. #1 · chrismdp ·

How an issue on chrismdp/awml becomes a merged pull request. A maintainer labels an issue build; Claude drafts the change, the checks run, two fresh sessions review it for bugs and security, and a classifier weighs its risk before the pull request opens. Every pull request from the repository's own people is then reviewed again as GitHub checks. Once CI has run, a rule merges a straightforward change or asks for review. A failed try starts the build again, up to three times.

MapChecksNo mistakesWho waitsWhere it runs
WorkflowAn issue becomes a pullrequest →WorkflowA pull request lands once CIhas run →A failed build tries againWorkflowA pull request is reviewed →In An issue becomes a pull requestTriggerThe build label is added to anissueIn An issue becomes a pull requestTriggerretry-a-build starts the buildagain for an issueIn A pull request lands once CI has runTriggerCI's pull_request run finisheson a build/issue-* branch ofthis repositoryIn A failed build tries againTriggerCI's tests fail on a pull_requestrun from a build/issue-*branch of this repository,whatever else failedStarts An issue becomes a pull requestOutside actionStart the build againAllowIn A pull request is reviewedTriggerA pull request from a branchof this repository, opened bysomeone with write access orby the app, is opened orpushed toIn An issue becomes a pull request, A pull request lands once CI has run, A failed build tries again and A pull request is reviewedConnectionThe repository, through itsown Actions tokenIn An issue becomes a pull request and A pull request lands once CI has runConnectionThe repository, through itsown GitHub App