Skip to content

Docs: push the deployment tag via CLI before publishing the GitHub release #1069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AronNovak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Docs: push the deployment tag via CLI before publishing the GitHub release #1069

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -391,8 +391,19 @@ Optionally you can specify which target branch you'd like to push on Pantheon, b
`ddev robo deploy:config-autodeploy [your terminus token] [your github token] [pantheon project name] [gh_branch] [pantheon_branch]`

After you have automatic deployment for a project, you are able to deploy to Pantheon `test` and `live` using Git tags.
`git tag 0.1.2` will imply a deployment to the `test` environment (and `dev` - as enforced by Pantheon).
`git tag 0.1.2_live` will imply a deployment to `live`. In order to make it fast, you need to first create the tag that deploy to `test`, then you need to tag the same commit with a tag suffixed with `_live`.

# Deploy to TEST (and DEV - as enforced by Pantheon).
git tag 0.1.2
git push origin 0.1.2

# Deploy to LIVE.
git tag 0.1.2_live
git push origin 0.1.2_live

In order to make it fast, you need to first create the tag that deploys to `test`, then you need to tag the same commit with a tag suffixed with `_live`.

> **Important:** Always push the tag with `git push origin <tag>` **before** publishing the GitHub release.
> Creating a tag exclusively through the GitHub release UI may not fire the `push` event that triggers the deployment workflow, so the deployment gets skipped silently.

### Manual Steps

Expand Down
Loading