Conversation
Author
|
@abonander The failing SQLite matrix job appears to be unrelated to this change. All five SQLCipher tests passed, but the test process subsequently exited with I don't have permission to rerun the upstream workflow. Could you please rerun the failed jobs when convenient? |
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
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.
Does your PR solve an issue?
Fixes #4389.
What does this PR change?
This adds support for customizing the initial contents of migrations generated by
sqlx migrate add.Users can place the following files in the migration source directory:
.template.sqlfor simple migrations.template.up.sqlfor reversible up migrations.template.down.sqlfor reversible down migrationsThe CLI copies the matching template into each newly created migration. If a template is absent, it retains the existing default contents.
Template files are excluded when resolving migrations, so they are not treated as migrations themselves.
The available templates and fallback behavior are documented in the CLI README and command help.
Is this a breaking change?
No. Existing behavior remains unchanged when no template files are present.
Testing
cargo +stable test -p sqlx-core --lib migrate::sourcecargo +stable test -p sqlx-cli --test addcargo +stable fmt --all -- --checkcargo +stable clippy -p sqlx-cli --tests --no-deps -- -D warnings