Github Action to Deploy to Production #168
Merged
Conversation
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
Coverage Report
File CoverageNo changed files found. |
|
ascibisz
changed the title
meganrm
approved these changes
Dec 12, 2025
rugeli
approved these changes
Dec 15, 2025
Contributor
rugeli
left a comment
rugeli
left a comment
There was a problem hiding this comment.
Looks good to me, thanks for adding the documentation too!
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.
Problem
The infrastructure team set us up with a AWS role that has OIDC configured to be able to write to our S3 bucket (or something like that, I don't know the details) so now we can have a github action to deploy our production site rather than doing it manually!
Link to story or ticket
Solution
I did a test commit setting up a github action writing to a subfolder of the bucket that was triggered by new PRs and everything worked as expected! Now I have it set up to only trigger based on git tag of new version, so I think we'll just have to wait and test that once we've merged.