refactor(schema): split baseline migrations by domain#45
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Splits the schema migrations into domain-oriented files so the migration folder is readable at a glance: users, teams/RBAC, auth sessions, incidents, timeline, external secrets, timeline reactions, bans, private messages, and releases.\n\nAlso marks .sqlx/** as GitHub Linguist generated so the SQLx offline cache no longer pollutes language/diff stats as product code.\n\nValidation:\n- Fresh disposable DB migration smoke passed with all 10 migrations.\n- cargo test -p opswarden-server passed.\n- SQLX_OFFLINE=true cargo check -p opswarden-server passed.\n- cargo fmt --all -- --check passed.\n- git diff --check passed.\n\nImportant alpha caveat: this rewrites migration history for readability. Existing local/dev databases with the old migration versions should be reset before running this branch/main after merge, e.g. docker compose down -v && docker compose up --build.