forked from mirrors/gotosocial
[chore] Update .drone.yml signature (#1052)
* [chore] Update .drone.yml signature * update contributing.md
This commit is contained in:
parent
1f256e288b
commit
9ebc29b0e1
2 changed files with 3 additions and 3 deletions
|
@ -182,6 +182,6 @@ steps:
|
|||
|
||||
---
|
||||
kind: signature
|
||||
hmac: db02a09af7262a2bab5a0cb4bfd82fa7e1dc566c29e55e6e0808e8f1dc92803b
|
||||
hmac: 2166c95bd8ba068c928aa4ec8645836a40fc2c99ceb5541b8c365763ee63e3b2
|
||||
|
||||
...
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue