startupmigrations: rename from sqlmigrations, add doc.go #67593
Merged
Conversation
This file contains 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
|
This change is |
ajwerner
force-pushed
the
ajwerner/rename-sqlmigrations
branch
from
bb8078d to
9077308
Compare
tbg
approved these changes
Jul 14, 2021
arulajmani
approved these changes
Jul 14, 2021
There was a problem hiding this comment.
Reviewed 32 of 32 files at r1, 1 of 2 files at r2.
Reviewable status:complete! 1 of 0 LGTMs obtained (waiting on @knz and @nvanbenschoten)
ajwerner
force-pushed
the
ajwerner/rename-sqlmigrations
branch
from
9077308 to
40c7d23
Compare
There was nothing particularly `sql` about these migrations except, maybe, that they had access to sql. Release note: None
Release note: None
ajwerner
force-pushed
the
ajwerner/rename-sqlmigrations
branch
from
40c7d23 to
d54cfc7
Compare
rickystewart
approved these changes
Jul 14, 2021
|
TFTR! bors r+ |
|
Build succeeded: |
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.
There was nothing particularly
sqlabout these migrations except, maybe,that they had access to sql.