summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorLibravatar tobi <31960611+tsmethurst@users.noreply.github.com>2022-11-15 17:02:50 +0100
committerLibravatar GitHub <noreply@github.com>2022-11-15 17:02:50 +0100
commit9ebc29b0e1f8b9f84ce53a3269dfc698af07d787 (patch)
treee93a16d0c88e4e42be089dbe65963edd70841f4a /CONTRIBUTING.md
parent[chore] refactor test/cliparsing.sh into a go test below internal/config (#1036) (diff)
downloadgotosocial-9ebc29b0e1f8b9f84ce53a3269dfc698af07d787.tar.xz
[chore] Update .drone.yml signature (#1052)
* [chore] Update .drone.yml signature * update contributing.md
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0633f58d0..3620b2cab 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -188,9 +188,9 @@ Finally, to run tests against both database types one after the other, use:
### CLI Tests
-In [./test/cliparsing.sh](./test/cliparsing.sh) and [./test/envparsing.sh](./test/envparsing.sh) there are a bunch of tests for making sure that CLI flags, config, and environment variables get parsed as expected.
+In [./test/envparsing.sh](./test/envparsing.sh) there's a test for making sure that CLI flags, config, and environment variables get parsed as expected.
-Although these tests *are* part of the CI/CD testing process, you probably won't need to worry too much about running them yourself. That is, unless you're messing about with code inside the `main` package in `cmd/gotosocial`, or inside the `config` package in `internal/config`.
+Although this test *is* part of the CI/CD testing process, you probably won't need to worry too much about running it yourself. That is, unless you're messing about with code inside the `main` package in `cmd/gotosocial`, or inside the `config` package in `internal/config`.
## Project Structure