Skip to main content

PR Merge → Spacelift Approval Workflow

Feature Requests

We run one stack per environment, pointing at the same Git ref. When a PR merges, multiple stack runs are triggered, but some require manual approval. Engineers often forget to manually confirm, which causes delays and errors.

An ability to tie the confirmation/approval of a Spacelift run back into the originating GitHub/GitLab PR, so that required confirmations happen in context of the PR would be really helpful

Workaround
No
Status: ⬆️ Gathering votes1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    Aug 27, 2025

    Thank you for this thoughtful feature request! You've identified a real workflow pain point that many teams experience.

    The good news is that you can actually achieve this workflow today using our existing policy framework, though it requires a bit more setup than a built-in feature would.

    Here's how you can solve this with current Spacelift capabilities:

    • Approval Policies can require confirmation for runs triggered by PR merges. You can write policies that detect post-merge runs and require specific approvals before they proceed.

    • Notification Policies can send alerts directly to your GitHub/GitLab PRs, Slack channels, or email when runs need confirmation. This keeps the workflow visible where your team is already working.

    • Push Policies can control exactly when runs are triggered and whether they require confirmation based on the PR context.

    For example, you could set up a notification policy that comments on the original PR when confirmation is needed, or sends a Slack message to the PR author with a direct link to confirm the run.

    While this approach requires configuring policies rather than having a built-in PR integration, it gives you much more flexibility to customize the workflow for your specific team needs and approval requirements.

    The underlying job you're trying to solve - ensuring engineers don't forget to confirm critical deployments - is definitely achievable with our current governance framework. Would you like help setting up policies to implement this workflow for your team?