commit | 7938acbadb9baeb3b2ad9b4d03e8de087e0d60ec | [log] [tgz] |
---|---|---|
author | Jonathan Amsterdam <jba@google.com> | Tue Dec 10 08:27:51 2019 -0500 |
committer | Julie Qiu <julie@golang.org> | Fri Mar 27 16:46:49 2020 -0400 |
tree | 492182546181879efcd2841e7afada911eb8b49a | |
parent | 5a50b60839e1eeb319af76e0a8caada011dddb6a [diff] |
internal/testing/htmlcheck: remove InAt The same can be achieved with CSS selectors, using :nth-child and :nth-of-type. Change-Id: I57486922d5d0060862b20d67f56be808b6c65082 Reviewed-on: https://team-review.git.corp.google.com/c/golang/discovery/+/617945 CI-Result: Cloud Build <devtools-proctor-result-processor@system.gserviceaccount.com> Reviewed-by: Robert Findley <rfindley@google.com>
Migrations are managed with the golang-migrate/migrate CLI tool.
To run all the migrations:
migrate -source file:migrations -database "postgres://localhost:5432/discovery-database?sslmode=disable" up
To create a new migration:
migrate create -ext sql -dir migrations -seq <title>
This creates two empty files in /migrations
:
{version}_{title}.up.sql {version}_{title}.down.sql
The two migration files are used to migrate “up” to the specified version from the previous version, and to migrate “down” to the previous version. See golang-migrate/migrate/MIGRATIONS.md for details.