Let CI be run on demand, since main is otherwise never verified #1072
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1072
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/dispatchable"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ci.ymlcould only be triggered by a push tomainor a pull request against it. Merging through the API does not reach the runner as a push event, so the default branch is the one branch nothing checks after it changes — which is how #776 landed green and leftmainred for hours.workflow_dispatchmakes verifying a branch something someone can choose to do, and it also kills a workaround that never worked: #930 documents pushing to a scratchci/main-verifybranch to get a run, butpush:is scoped tobranches: [main], so that push matches no trigger at all.Nothing about the matrix changes — same three jobs, same Node versions, same steps.
While investigating this I found the scheduled-workflow deadlock (#1071) and the runner running with
capacity: 1on a 40-core host; both are covered there.