Skip to content

Commit 86cd5ec

Browse files
committed
Fix markdown links
1 parent 7fa0191 commit 86cd5ec

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -97,8 +97,8 @@ much data as possible.
9797
There are two types of fixtures that are used to test that migrations don't
9898
break existing Coder deployments:
9999

100-
- Partial fixtures [`migrations/testdata/fixtures`](./coderd/database/migrations/testdata/fixtures)
101-
- Full database dumps [`migrations/testdata/full_dumps`](./coderd/database/migrations/testdata/full_dumps)
100+
- Partial fixtures [`migrations/testdata/fixtures`](../coderd/database/migrations/testdata/fixtures)
101+
- Full database dumps [`migrations/testdata/full_dumps`](../coderd/database/migrations/testdata/full_dumps)
102102

103103
Both types behave like database migrations (they also [`migrate`](https://github.com/golang-migrate/migrate)). Their behavior mirrors Coder migrations such that when migration
104104
number `000022` is applied, fixture `000022` is applied afterwards.
@@ -119,7 +119,7 @@ $ ./coderd/database/migrations/create_fixture.sh my fixture
119119
```
120120

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

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

0 commit comments

Comments
 (0)