Fallout-build / Fallout-build/Fallout
Approval-gate provider abstraction (platform-delegated or Fallout-server)
Open
enhancement
RFC
target/vNext
- Dominant language
- C#
- Stars
- 154
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 15
Description
Part of #332.
A human "approve deploy" gate cannot live inside a build process — it's the one irreducibly-external piece. Model it as a **pluggable provider**:
- **Delegated** — GitHub Environments required-reviewers, Octopus manual-intervention, Azure DevOps approvals.
- **Standalone** — a Fallout-server approval when self-hosted (ties to the agent/runner #113).
RFC the gate contract (how a target/environment declares it needs approval, how the provider satisfies it, timeout/abort semantics).
Contributor guide
Assessment
This issue has not been assessed yet.