GitHub delivery and recovery
Understand development delivery, promotion, candidates and releases.
This is an extension used by Clowld Space's own development workflow. It requires GitHub permissions and matching branches, checks and release workflows. Connecting an arbitrary repository does not install a complete release pipeline. Start with GitHub integration.
Four stages
| Stage | Action | Completion |
|---|---|---|
| Development | Open a feature PR against dev and request Auto-merge | A queued request is pending; only an actual merge delivers it to the branch |
| Promotion | Merge a verified dev snapshot into main through a promote/* PR | The promotion PR is merged |
| Candidate | Build and verify artifacts for an exact commit | The candidate workflow succeeds and its proof matches the bound issue |
| Release | Create an authorized version tag and run the release workflow | The formal release workflow succeeds; a candidate alone is not a release |
After requesting Auto-merge, the development agent can end its handoff while GitHub handles checks and merging. Issue completion still depends on closing keywords and other open associated PRs; see GitHub integration.
Failure reports
The issue timeline receives the result, PR or workflow link, commit and failed job. Development recovery requires a failed Dev PR Gate on the current head of an open PR. Drafts, obsolete heads and cancellation-only development checks do not start a new recovery.
Promotion uses Promotion Gate. With Actions read access and workflow_job events, a failed job can be reported early; otherwise the overall result can still report failure. Candidate and release results must match their issue bindings.
Recovery and escalation
Eligible failures are handed to the system coordinator Coco for investigation. An available agent, runtime and execution permissions are still required; a failure comment does not prove a repair ran. Duplicate webhooks do not count as new recovery rounds, but a new failed attempt on the same commit can count.
Two consecutive matching failures or three failed recovery rounds stop automatic recovery and request a human decision. Promotion, candidate and release escalation preserves the assignee. Inspect the timeline and linked errors, resolve the blocker and continue within existing authorization. Pending, retried or triggered is not successful.
Promotion success does not grant release permission. Release intent must be confirmed through the workflow before an unauthorized release can proceed.
This describes current code. Check the automatic-completion settings in GitHub integration and the version guide when using an older backend.