Version 0.9.5 of the 'Push to Pantheon' GitHub Action is now available.
This release changes how the action handles a push that has no Pantheon environment to deploy to, and corrects the documentation for the target_env and target_env_strategy inputs.
What's new
A Multidev comes from a pull request. A push to any other branch has nothing to derive an environment name from.
In 0.9.4 the action treated that as an error and failed the job, so adding the action to a workflow that runs on every push would fail on a feature branch with no PR. In 0.9.5 the action skips the remaining steps and the job succeeds, and the step log records why the deployment was skipped.
A misconfiguration still fails the job: a target_env value Pantheon will not accept, an unrecognized target_env_strategy, or the branch strategy with no branch to read.
If you want pushes to other branches to deploy, set target_env_strategy: branch to deploy to a Multidev named after the branch, or set target_env explicitly. (#188)
How to upgrade to 0.9.5
Update your workflow file to use 0.9.5:
For more information about this release, see the GitHub release page. To learn more about deploying to Pantheon from GitHub, see GitHub Actions.
If you have questions or concerns about the action, please use the Push to Pantheon issue queue.
