Skip to content

Commit 511ca6b

Browse files
kevinlnewclaude
andcommitted
docs(rfc): add promote (ff-only push) operation to runway workflow
Address review feedback: document the promote operation that pushes a commit to a ref as-is (--ff-only), e.g. forwarding a landed SHA from main to verified/main using the PROMOTE merge strategy. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 7d0e00a commit 511ca6b

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

doc/rfc/runway/workflow.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ The two queues operate at different granularities:
1010

1111
- **merge** is batch-level. A merge request carries the same payload but Runway commits the result and reports the revisions it produced (per-step output IDs).
1212

13+
A third operation — **promote** — pushes a commit to a ref as-is (`--ff-only`). The primary use case is forwarding a landed SHA from `main` to `verified/main` without creating a new merge commit. Promote reuses the merge queue with the `PROMOTE` merge strategy; Runway fast-forwards the target ref and reports the same SHA back as the output ID.
14+
1315
These are independent input-output flows. A merge-conflict check can run without a merge ever running, and a merge does not depend on a prior check.
1416

1517
## Branch serialization

0 commit comments

Comments
 (0)