Version 0.9.7 of the Push to Pantheon GitHub Action is now available.
This release adds inputs that control what a new Multidev clones from its source environment, and makes the target_env input more forgiving about capitalization.
What's new
- Control what new Multidevs clone: Two new optional inputs,
clone_filesandclone_database, control what the action copies fromsource_envwhen it creates a Multidev. Both default totrue, so existing workflows behave as before. Set either tofalseto skip that content (the action passes--no-filesor--no-dbtoterminus multidev:create). This is useful when a Multidev only needs code, or when cloning a large database or files directory slows down every pull request. The inputs only apply when the action creates the Multidev. They have no effect on a Multidev that already exists. They also don't apply when the action deploys with Terminus Build Tools, which creates the Multidev itself. In that case the action logs a warning if either input is set tofalse. (#199) - Uppercase
target_envvalues are lowercased: Pantheon environment names must be lowercase. In 0.9.4 through 0.9.6, atarget_envwith uppercase letters failed the deployment with a message that the name was not a valid Pantheon environment. The action now lowercases the value and logs a message noting the change. Other naming problems, such as underscores, and reserved names likemaster, are still rejected. Branch names longer than 11 characters are still truncated to a maximum of 11 characters. (#200)
Example
This workflow step creates new Multidevs with code only, without copying the database or files from the source environment:
How to upgrade to 0.9.7
Update your workflow file to use 0.9.7:
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, ask in Pantheon Community Slack or use the Push to Pantheon issue queue.