lavender-legacy/gitea
7
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Specify relation between multiple signing options (#15496)

Browse source
This commit is contained in:
firesoft-de 2021-04-15 18:06:32 +02:00 committed by GitHub
parent 2a42d80d14
commit af2adb4e35
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/content/doc/advanced/signing.en-us.md
View file

@ -109,7 +109,7 @@ when creating a repository. The possible values are:
- `always`: Always sign
Options other than `never` and `always` can be combined as a comma
separated list.
separated list. The commit will be signed if all selected options are true.
### `WIKI`
@ -123,7 +123,7 @@ The possible values are:
- `always`: Always sign
Options other than `never` and `always` can be combined as a comma
separated list.
separated list. The commit will be signed if all selected options are true.
### `CRUD_ACTIONS`
@ -137,7 +137,7 @@ editor or API CRUD actions. The possible values are:
- `always`: Always sign
Options other than `never` and `always` can be combined as a comma
separated list.
separated list. The change will be signed if all selected options are true.
### `MERGES`
@ -154,7 +154,7 @@ The possible options are:
- `always`: Always sign
Options other than `never` and `always` can be combined as a comma
separated list.
separated list. The merge will be signed if all selected options are true.
## Obtaining the Public Key of the Signing Key