Merged
Conversation
When we deploy to production we run the script create-deplyoment-issue to create the github issue for the deployment. This makes that step automatic, when running the deploy-production script we'll automatically create that issue if it doesn't already exist, and if it exists and has already been closed, we'll abort the deployment.
…open release issues at the end of a production deployment.
jcscottiii
approved these changes
Oct 9, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When we deploy to production we run the script create-deplyoment-issue to create the github issue for the deployment. This makes that step automatic, when running the deploy-production script we'll automatically create that issue if it doesn't already exist, and if it exists and has already been closed, we'll abort the deployment.