Why isn't Porter detecting pushes to a new deployment branch?
Last updated: April 28, 2025
If you've updated your Porter YAML files to deploy from a new branch but deployments aren't being triggered on push, make sure that your GitHub workflow files are also present in the target branch.
Common scenarios
You've updated your Porter YAML to point to a new branch (e.g. from 'main' to 'staging')
You're pushing code to the new branch but no deployments are triggered
The workflow files exist in your original branch but not in the new target branch
Solution
Ensure that your GitHub workflow files (typically located in .github/workflows/) are copied to or present in the new branch you want to deploy from. These files contain the necessary triggers and actions for Porter to detect changes and initiate deployments.
Tip: When switching deployment branches, always remember to migrate both your Porter YAML configuration files and the associated GitHub workflow files to the new branch.