fix(db-migrations): Update instructions on db migrations#16200
Merged
suejung-sentry merged 2 commits intomasterfrom Feb 2, 2026
Merged
fix(db-migrations): Update instructions on db migrations#16200suejung-sentry merged 2 commits intomasterfrom
suejung-sentry merged 2 commits intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
suejung-sentry
force-pushed
the
sshin/db-migration-devdocs
branch
from
61446f6 to
2fd1703
Compare
wedamija
approved these changes
Jan 29, 2026
Member
wedamija
left a comment
wedamija
left a comment
There was a problem hiding this comment.
Nice, I think there might be a test that hassles you about this, but even easier to just do it up front.
markstory
approved these changes
Jan 29, 2026
Member
Author
Oh gotcha, I didn't see that test failure, but did get a note from the code review bot here and also when looking for examples this was last done, saw this helpful instruction |
Member
Author
|
Will wait for a review from docs team then merge! |
coolguyzone
reviewed
Feb 2, 2026
Contributor
coolguyzone
left a comment
coolguyzone
left a comment
There was a problem hiding this comment.
LGTM! Thanks for updating! 🏄♂️
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
4 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.
DESCRIBE YOUR PR
Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
I did a delete table flow the other day and got some good tips on my PR from the db experts that I wanted to leave for the next person.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES