Skip to content

Conversation

@bcrant
Copy link

@bcrant bcrant commented Nov 12, 2025

What does this PR do?

On final step of CI/CD, applying plan to prod, exit early (raise an error) before applying plan to prod if the PR merge state status is "blocked".

Why?
It is currently possible for synchronized deployments to get into a bad state, where the changes in a PR have been applied to the production environment but have not been merged (desychronized), with the following configurations:

  • Sychronized deployment
  • CI/CD Bot configured to use Deploy Command Signal
  • CI/CD Bot is NOT configured to use Required Approval Signal
  • Repository has Github CODEOWNERS branch protection rules

This is currently possible because the GithubController.deploy_to_prod() checks explicitly checks for "is_dirty" state, but if the only thing missing is CODEOWNER approval, the merge state status "is_blocked", not "is_dirty".
https://docs.github.com/en/enterprise-cloud@latest/graphql/reference/enums#mergestatestatus

…issing CODEOWNERS approval, this is breaking synchronous deployments.
@CLAassistant
Copy link

CLAassistant commented Nov 12, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants