Skip to content

Commit 7f6517d

Browse files
committed
fix links
1 parent 90b7199 commit 7f6517d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/contributing/backend.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -169,9 +169,9 @@ There are two types of fixtures that are used to test that migrations don't
169169
break existing Coder deployments:
170170

171171
* Partial fixtures
172-
[`migrations/testdata/fixtures`](../coderd/database/migrations/testdata/fixtures)
172+
[`migrations/testdata/fixtures`](../../coderd/database/migrations/testdata/fixtures)
173173
* Full database dumps
174-
[`migrations/testdata/full_dumps`](../coderd/database/migrations/testdata/full_dumps)
174+
[`migrations/testdata/full_dumps`](../../coderd/database/migrations/testdata/full_dumps)
175175

176176
Both types behave like database migrations (they also
177177
[`migrate`](https://github.com/golang-migrate/migrate)). Their behavior mirrors
@@ -194,7 +194,7 @@ To add a new partial fixture, run the following command:
194194
```
195195

196196
Then add some queries to insert data and commit the file to the repo. See
197-
[`000024_example.up.sql`](../coderd/database/migrations/testdata/fixtures/000024_example.up.sql)
197+
[`000024_example.up.sql`](../../coderd/database/migrations/testdata/fixtures/000024_example.up.sql)
198198
for an example.
199199

200200
To create a full dump, run a fully fledged Coder deployment and use it to

0 commit comments

Comments
 (0)