requests

Overview ¶

Command requests creates changes, enqueues each as a land request, and watches them move through the pipeline — so the demo stack can be exercised repeatedly without authoring changes by hand.

Nothing is awaited until the end, which is the point. Each change is enqueued the moment it is created, so the queue is already working on the first while the last is still being made. A queue that only ever holds one request in flight never batches, never analyzes a conflict against another batch, and never speculates; those behaviors only appear when requests overlap. The table watches all of them at once.

Independent changes are created several at a time (-concurrency), since nothing about them depends on the others — which matters most against a provider, where each is several round trips. A stack cannot be: every change in it is based on the branch before it, so the next cannot be cut until the previous head exists.

Two shapes of change, because the pipeline treats them differently:

• independent (default): each change targets the base branch and is enqueued as its own request, immediately after it is created. This is what puts requests in flight against each other.
• stacked (-stacked): each change is based on the one before it, and all of them go in as a single request once the chain exists — the atomic-stack path, where the whole set reaches the target in one push.

The table is drawn before the first change exists and refreshed for the whole run, so there is never a stretch with nothing to look at. Each row is one land request and shows the states it has passed through, read from the gateway's history API rather than sampled — polling only the current status would miss any transition that happens between two ticks, which for a fast queue is most of them.

How a change is made depends on -provider, matching the stack the run is pointed at:

• fake (default): a change is a URI and nothing else. No repository, no credential, no I/O — the fastest way to put traffic through the queue.
• git: a branch pushed to the sandbox repository the stack merges into. Real commits, still no credential.
• github: a real pull request over the REST API, which needs no clone and no git binary, only GITHUB_TOKEN — the same credential the stack uses.