docs: fix a few broken links to migrations and fixtures page - #3556
Merged
Conversation
jgravois
marked this pull request as draft
March 5, 2026 16:37
jgravois
force-pushed
the
docs/link-fixes
branch
from
March 5, 2026 16:40
3e3cdad to
d7de317
Compare
Member
|
Huh, I didn't notice that before, but I see it now, too. IIRC, databases keep track of auto-incrementing PKs and won't restart them without some additional effort. |
Scotchester
approved these changes
Mar 5, 2026
Scotchester
left a comment
Member
There was a problem hiding this comment.
Thank you, and sorry I neglected to test these links.
jgravois
marked this pull request as ready for review
March 5, 2026 16:48
Contributor
jgravois
force-pushed
the
docs/link-fixes
branch
from
March 5, 2026 17:44
d7de317 to
8bcf07b
Compare
Contributor
|
Preview url: https://benefits-3556--cal-itp-previews.netlify.app |
Member
Author
truly no biggie 🤗 |
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.
just something small i noticed when i tested #3546 locally.
one thing that surprised me was that the ids in the
django_migrationstable didn't reset when i faked the migrations after blowing away all the previous rows.i assume its harmless. i was just temporarily at a loss thinking that somehow @Scotchester's PR was able to preserve the original migration history without the files 😆