docs: add Third-party Tools section with pytest-mrt#1818
Open
croc100 wants to merge 1 commit into
Open
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.
Adds a Third-party Tools section to
front.rstfor community projects that complement Alembic but don't fit the existing autogenerate extensions section.First entry is pytest-mrt — a pytest plugin that tests whether migrations are safely reversible. Runs the actual up/down cycle with real data, and also does static analysis on migration files (missing downgrade, DROP COLUMN, no-op downgrade, etc.).
The autogenerate "Notable 3rd-party libraries" section felt too narrow for this — it's scoped to autogenerate extensions. Wasn't sure where else to put it so went with a new section between Community and Bugs.