... | ... | @@ -289,7 +289,12 @@ particular, you might want to use `private=yes;channel=tor-foo` if you |
|
|
do not want to have the bot send notifications in `#tor-bots`, which
|
|
|
is also does by default.
|
|
|
|
|
|
> **NOTE**: If you tell the bot to send a notification to the channel `#tor-foo`, but the bot can't access `tor-foo` (because it lacks permission, doesn't have the channel password, etc.) then the bot will default to `#tor-bots`. Be careful to not accidentally leak sensitive information to a public channel!
|
|
|
> **IMPORTANT**: Again, even if you tell the bot to send a
|
|
|
> notification to the channel `#tor-foo`, the bot still defaults to
|
|
|
> *also* sending to `#tor-bots`, unless you use that `private` flag
|
|
|
> above. Be careful to not accidentally leak sensitive information to
|
|
|
> a public channel, and test with a dummy repository if you are
|
|
|
> unsure.
|
|
|
|
|
|
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
|
... | ... | |