awml
Sign in

chrismdp / issue-to-pull-request

An issue becomes a pull request

Public ·
Version 7 of 23
  1. #23 · chrismdp · · 0.8Latest
  2. #22 · chrismdp · · 0.6
  3. #21 · chrismdp · · 0.6
  4. #20 · chrismdp · · 0.6
  5. #19 · chrismdp · · 0.6
  6. #18 · chrismdp · · 0.6
  7. #17 · chrismdp · · 0.6
  8. #16 · chrismdp · · 0.4
  9. #15 · chrismdp · · 0.4
  10. #14 · chrismdp · · 0.4
  11. #13 · chrismdp · · 0.4
  12. #12 · chrismdp · · 0.4
  13. #11 · chrismdp · · 0.4
  14. #10 · chrismdp · · 0.4
  15. #9 · chrismdp · · 0.4
  16. #8 · chrismdp · · 0.3
  17. #7 · chrismdp · · 0.3Showing
  18. #6 · chrismdp · · 0.3
  19. #5 · chrismdp · · 0.3
  20. #4 · chrismdp · · 0.3
  21. #3 · chrismdp · · 0.3
  22. #2 · chrismdp · · 0.3
  23. #1 · chrismdp · · 0.3
Fork
Who may see each partWhere each part runsYAMLChecks2mistakes

platform.yaml has 1 mistake, drawn in red. See Checks.

GitHub: issues, branches, pull requestsActions job: draft, with a read-only tokenActions job: checks, with a read-only tokenActions job: branch, pull request and merge, running nothing from the changeThe maintainer's browserClaude Code, claude-opus-5-5, on the maintainer's subscriptionthe label[build]the issue's threadthe issue and its people'scomments[all pass][opened][straightforward][needs a review]outside action "mainauto" isAsk, but part "automerge"leads to it with no person inbetweenthe pull requestTriggerThe build label is added to anissueOnly people with write access can add a label, and GitHub holds that, not a prompt, so a stranger's comment starts nothing. The draft step's token can only read, so it can't push (awml #26)Used by chrismdp/ci-a-commit, chrismdp/fix-review-findings, chrismdp/land-a-pull-request, chrismdp/rebase-conflicting-pull-requests, chrismdp/retry-a-build and chrismdp/review-a-pull-requestConnectionThe repository, through itsown Actions tokenCode · sortSort by rule: is the label build?Code · bring-inBring in the issue and thecomments of the repository'sown peopleAnyone can comment, but the bring-in step passes on only the comments of the owner, members and collaborators, so strangers' text never reaches the draft step. AWML can't mark this yet (awml #5)DataThe spec, guide, code andAGENTS.mdAI · draftWrite the change test firstDataThe change, as a patch, withClaude's note on itCode · checkRun the tests, vet, theexamples and wasm parityThe check runs where the draft step can't reach, and its verdict is in its own record (awml #13, #20)Code · doPush a branch and open a pullrequest that closes the issueOutside actionOpen the pull requestAllowDataThe build rules: what needs areview, and the daily limitCode · sortSort by rule: is the changestraightforward?Claude's note can send a change to review but can't skip one. The rule reads the patch itself: what it touches, its size and whether it deletes a test (awml #20, #26)Code · doMerge the pull request, sayingin its message why it wasstraightforwardA merge by the Actions token doesn't start CI or the rebase workflow, so the merge step starts the rebase workflow itselfOutside actionMerge into mainAsk, under the maintainer's standing approvalStanding approval from the maintainer: only changes the rule finds straightforward, up to five a day. Each is undone with git revert, and its pull request says so. A new install takes main, but existing installs update only at a release, which stays the maintainer's yesConnectionThe repository, through themaintainer's accountPerson · doReview the pull request andmerge itOutside actionMerge into mainAsk