Files
OmniRoute/scripts
diegosouzapw 9cc93e77ed fix(ci): omni-queue lands only a candidate that is the composition of its stored batch
The tick blessed and landed whatever the stored in-flight record named: a
record with no PR, or a candidate with an extra commit, got the land status.
Before the would-land and the bless, land.verifyComposition now requires a
non-empty batch, the base as an ancestor of the candidate, a first-parent
chain made only of queue merge commits that the stored PRs consume in order
at their heads, and stacked PRs (no merge commit of their own) exactly where
composeCandidate puts them; squash-api also checks the stored tree. A
mismatch blesses and lands nothing, records no would-land, and pauses the
queue with reason "error".
2026-11-15 07:34:25 -03:00
..
2026-06-19 06:49:01 -03:00
2026-06-23 17:06:18 -03:00
2026-10-19 12:22:25 -03:00
2026-10-19 12:22:25 -03:00
2026-11-12 12:29:18 -03:00
2026-11-12 12:29:18 -03:00
2026-07-29 15:18:55 -03:00
2026-09-29 19:58:13 -03:00
2026-07-13 09:12:40 -03:00