... | @@ -294,6 +294,25 @@ is also does by default. |
... | @@ -294,6 +294,25 @@ is also does by default. |
|
> a public channel, and test with a dummy repository if you are
|
|
> a public channel, and test with a dummy repository if you are
|
|
> unsure.
|
|
> unsure.
|
|
|
|
|
|
|
|
The KGB bot can also send notifications to channels that require a password.
|
|
|
|
In the `/etc/kgb.conf` configuration file, add a `secret` to a channel so the
|
|
|
|
bot can access a password-protected channel. For example:
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
channels:
|
|
|
|
-
|
|
|
|
name: '#super-secret-channel
|
|
|
|
network: 'MyNetwork'
|
|
|
|
secret: 'ThePasswordIsPassw0rd'
|
|
|
|
repos:
|
|
|
|
- SecretRepo
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: support for channel passwords is not implemented in the upstream KGB
|
|
|
|
> bot. There's an [open merge request](https://salsa.debian.org/kgb-team/kgb/-/merge_requests/8)
|
|
|
|
> for it and the patch has been applied to TPA's KGB install, but new installs
|
|
|
|
> will need to manually apply that patch.
|
|
|
|
|
|
Note that GitLab admins might be able to configure [system-wide
|
|
Note that GitLab admins might be able to configure [system-wide
|
|
hooks](https://gitlab.torproject.org/help/system_hooks/system_hooks) in [the admin section](https://gitlab.torproject.org/admin/hooks), although it's not entirely clear
|
|
hooks](https://gitlab.torproject.org/help/system_hooks/system_hooks) in [the admin section](https://gitlab.torproject.org/admin/hooks), although it's not entirely clear
|
|
how does relate to the per-project hooks so those have not been
|
|
how does relate to the per-project hooks so those have not been
|
... | | ... | |