awml
Sign in

chrismdp / rebase-conflicting-pull-requests

A pull request that conflicts with main is rebased onto it

Public ·
Version 1 of 4
  1. #4 · chrismdp · · 0.8Latest
  2. #3 · chrismdp · · 0.4
  3. #2 · chrismdp · · 0.4
  4. #1 · chrismdp · · 0.3Showing
Fork
Who may see each partWhere each part runsYAMLChecksNo mistakes
publicanyone who reads the repositorythe pushopen pull requests and whethereach conflicts[for each that conflicts][the repository's own][all pass][pushed or refused][any fail][gave up]TriggerA commit lands on mainConnectionThe repository, through itsown Actions tokenCode · bring-inBring in the open pull requeststhat conflict with mainCode · sortSort by rule: is the branch inthis repository, opened by itsown people or the buildworkflow?A fork's pull request, or one opened by a stranger, is never touched, so every line Claude reads was written by the repository's own people. AWML can't mark this yet (awml #5)DataThe branch's commits, main,and AGENTS.mdAI · draftRebase the branch onto main,keeping both sides of eachconflictDataThe rebased branch, as abundleCode · checkCheck it sits on main, has noconflict markers or workflowchanges, and passes everycheckA push by the Actions token doesn't start CI, so the check step's own run is the only check on the rebased branch until the maintainer pushesCode · doForce-push the rebasedbranch, only if it hasn't movedThe draft step's token can only read, so it can't push. The push names the commit the bring-in step saw, so GitHub refuses it if anyone pushed meanwhile (awml #26)Outside actionReplace the pull request'sbranchAllowAllow, because the old commit stays on GitHub and the comment names it, so the branch can be put back with one pushCode · doComment what was resolved,or why it couldn't beSurfaceThe pull request's thread