Add Migration CI #128
Merged
Add Migration CI #128
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
banushi-a
approved these changes
Feb 9, 2025
| @@ -3,7 +3,8 @@ | |||
| Cooper is a tool for Northeastern students to both submit reviews of their co-ops and filter through reviews of co-ops left by other students. | |||
|
|
|||
| ## The Cooper Docs | |||
| Read our docs [cooper-docs-sandboxney.verce.app](https://cooper-docs-sandboxneu.vercel.app/) ! | |||
|
|
|||
| Read our docs [cooper-docs-sandboxneu.vercel.app](https://cooper-docs-sandboxneu.vercel.app/) ! | |||
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.
Description
Add a GitHub Action workflow for running migrations on the production database (only for changes to
main).Motivation and Context
To reduce "points of failure" (forgot to run
pnpm db:generate, forgot to runpnpm db:migrateon the production database, accidentally forgot to switch back to development database, etc).How has this been tested?
Lemme think about this one 😛
Edit: Made it so that the CI also runs on all pull requests (temporarily) and spent half an hour trying to fix the
Missing POSTGRES_URLonly to realize that it is supposed to be a Repository Secret and not an Actions Secret (which still doesn't make sense to me but it works?).Screenshots (if appropriate):
Types of changes
Checklist: