Migrations reminder #15423
Closed
Migrations reminder #15423
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
github-actions
bot
added
Frontend
saraycp
force-pushed
the
migrations_reminder
branch
2 times, most recently
from
93d5465
to
eca6c1a
Compare
saraycp
force-pushed
the
migrations_reminder
branch
7 times, most recently
from
734a349
to
5d6e4de
Compare
saraycp
force-pushed
the
migrations_reminder
branch
from
5d6e4de
to
03f4ec4
Compare
|
Could be that you need to run the migrations locally and upload the new schema file? |
The check "Migrations Reminder" is failing due to permissions stuff. The exact same GitHub action works in another repo I have for testing. But it doesn't work in this repository. Still trying to figure out... |
|
This is already covered in #15824 |
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.
Instead of having a GitHub check that needs to pass, we better have a comment in the PR as a reminder.
The purpose is to warn that the migrations and related code changes should be shipped separately. We don't need to complicate things much.