mirror of
https://github.com/hoernschen/dendrite.git
synced 2024-12-26 15:08:28 +00:00
Fix scripts path in documentation (#1294)
Broken by 24d8df664c
Signed-off-by: Olivier Charvin <git@olivier.pfad.fr>
This commit is contained in:
parent
4b2db1dff5
commit
466d795375
2 changed files with 6 additions and 6 deletions
|
@ -12,9 +12,9 @@ directive](https://github.com/golangci/golangci-lint#nolint), e.g. `var
|
|||
bad_name int //nolint:golint,unused`. This should be used sparingly and only
|
||||
when its clear that the lint warning is spurious.
|
||||
|
||||
The linters can be run using [scripts/find-lint.sh](scripts/find-lint.sh)
|
||||
The linters can be run using [build/scripts/find-lint.sh](/build/scripts/find-lint.sh)
|
||||
(see file for docs) or as part of a build/test/lint cycle using
|
||||
[scripts/build-test-lint.sh](scripts/build-test-lint.sh).
|
||||
[build/scripts/build-test-lint.sh](/build/scripts/build-test-lint.sh).
|
||||
|
||||
|
||||
## Labels
|
||||
|
|
|
@ -16,9 +16,9 @@ As of May 2019, we're not using `gb` anymore, which is the tool we had been
|
|||
using for managing our dependencies. We're now using Go modules. To build
|
||||
Dendrite, run the `build.sh` script at the root of this repository (which runs
|
||||
`go install` under the hood), and to run unit tests, run `go test ./...` (which
|
||||
should pick up any unit test and run it). There are also [scripts](scripts) for
|
||||
[linting](scripts/find-lint.sh) and doing a [build/test/lint
|
||||
run](scripts/build-test-lint.sh).
|
||||
should pick up any unit test and run it). There are also [build/scripts](/build/scripts) for
|
||||
[linting](/build/scripts/find-lint.sh) and doing a [build/test/lint
|
||||
run](/build/scripts/build-test-lint.sh).
|
||||
|
||||
As of February 2020, we are deprecating support for Go 1.11 and Go 1.12 and are
|
||||
now targeting Go 1.13 or later. Please ensure that you are using at least Go
|
||||
|
@ -49,7 +49,7 @@ To save waiting for CI to finish after every commit, it is ideal to run the
|
|||
checks locally before pushing, fixing errors first. This also saves other people
|
||||
time as only so many PRs can be tested at a given time.
|
||||
|
||||
To execute what Buildkite tests, first run `./scripts/build-test-lint.sh`; this
|
||||
To execute what Buildkite tests, first run `./build/scripts/build-test-lint.sh`; this
|
||||
script will build the code, lint it, and run `go test ./...` with race condition
|
||||
checking enabled. If something needs to be changed, fix it and then run the
|
||||
script again until it no longer complains. Be warned that the linting can take a
|
||||
|
|
Loading…
Reference in a new issue