Files
gstack/docs
garrytanandcapy-ai[bot] 426fa370ec docs(ship-policy): a lagging merge ref is a scratch merge, not QUEUE_SCREEN_STALE_REF
Three passages still described the pre-scratch-merge refusal; they now
match screenMerge: a missing or lagging refs/pull/<n>/merge gets a
screen/<pr>-<head12> scratch merge, and QUEUE_SCREEN_STALE_REF is a real
conflict with the base only.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-10-26 16:12:57 +00:00
..