verify: live check of a CI-gated merge scheduling auto-merge-on-green (#438) #477
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "verify-438-head"
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?
Throwaway PR against a temporary protected scratch branch. The base requires the status check
gate-438, which nothing reports, so the merge is CI-gated. I merge this through madtea to confirm the live forge wording of the 405 and that a 2xx on the schedule request queues a real auto-merge. Never merges to main; the branches and the rule go away after.Refs #438.