fluxcd
/
notification-controller
mirror of https://github.com/fluxcd/notification-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: fix up typos in providers document and changelog 

Signed-off-by: ttyS3 <ttys3.rust@gmail.com>
This commit is contained in:
ttyS3 2022-12-28 14:31:31 +08:00
parent c19b434e8d
commit bfafab8e1e
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@ -32,7 +32,7 @@ Fixes:
This prerelease graduates the notification APIs to `v1beta2`. This prerelease graduates the notification APIs to `v1beta2`.
In addition, this version comes with support for In addition, this version comes with support for
[Gitea commit status updates](https://github.com/fluxcd/notification-controller/blob/api/v0.30.0/docs/spec/v1beta2/provider.md#gitea). [Gitea commit status updates](https://github.com/fluxcd/notification-controller/blob/api/v0.30.0/docs/spec/v1beta2/providers.md#gitea).
### `notification.toolkit.fluxcd.io/v1beta2` ### `notification.toolkit.fluxcd.io/v1beta2`

4
docs/spec/v1beta2/providers.md
View File

@ -1318,7 +1318,7 @@ the BitBucket repository specified in `.spec.address`.
You can create the secret with `kubectl` like this: You can create the secret with `kubectl` like this:
```shell ```shell
kubectl create secret generic gitlab-token --from-literal=token=<username>:<app-password> kubectl create secret generic bitbucket-token --from-literal=token=<username>:<app-password>
``` ```
#### Azure DevOps #### Azure DevOps
@ -1331,7 +1331,7 @@ The token must have permissions to update the commit status for the Azure DevOps
You can create the secret with `kubectl` like this: You can create the secret with `kubectl` like this:
```shell ```shell
kubectl create secret generic github-token --from-literal=token=<AZURE-TOKEN> kubectl create secret generic azuredevops-token --from-literal=token=<AZURE-TOKEN>
``` ```
## Provider Status ## Provider Status