Pull requests

GantryCD can create a preview plan when a pull request opens or receives a new commit. The preview does not apply and does not block normal deployments.

By default, someone must approve the preview before it runs. Pull request code has not been merged yet, but its providers and modules still run with the stack’s credentials. Automatic previews are best kept for repositories where all pull request authors are trusted.

The latest commit replaces any preview that is still waiting. Closing the pull request ends its preview.

Promotion

Promoting a successful preview creates a normal deployment from the pull request commit. GantryCD plans again, then follows the usual approval and apply flow. The preview itself is never applied.

A stack can require approvals or named CI checks before a preview runs or a pull request can be promoted. Missing and unfinished checks do not pass. Keep the list limited to checks that must block infrastructure changes.

Source control must be connected before GantryCD can receive pull request events. See Repositories.