ci: deploy to dev-orange with PR label #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boringcactus
added
the
deploy to dev-orange
boringcactus
temporarily deployed
to
dev-orange
GitHub Actions
Inactive
boringcactus
temporarily deployed
to
dev-orange
GitHub Actions
Inactive
boringcactus
temporarily deployed
to
dev-orange
GitHub Actions
Inactive
KaylaBrady
approved these changes
Nov 15, 2023
| @@ -1,4 +1,5 @@ | |||
| name: Deploy to Staging | |||
| run-name: ${{ github.event_name == 'workflow_dispatch' && format('Deploy {0} {1} to Staging', github.ref_type, github.ref_name) || '' }} | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As requested, this sets up automatic deployments to dev-orange based on a PR label. It also adds a somewhat nicer run title for manual deploys, since that overlaps somewhat with having a nice message in Slack describing what was deployed (which turns out to be surprisingly annoying when what's deployed is a PR).
Since this repo will at some point become public, we may eventually need to ensure that this only gets run for PRs that we wrote ourselves, even if we aren't quite paying attention and we apply the label to a PR coming in from outside. I'm not sure how best to do that, though.
I wish very much that GitHub Actions used a real programming language with actual conditionals and local variables.