Using IRC notifications via KGB with GitLab webhooks from salsa.debian.org
If you want to try KGB notifications, go to Settings→Webhooks and add a new webhook pointing to
For the channel parameter leading hash signs are optional and should be URL-encoded if present (%23).
Additional parameters may be added to the URL:
| parameter and default value | description |
|---|---|
network=oftc |
channel's network; the other supported networks are freenode and libera
|
private=0 |
omit copying each notification to #commits on freenode and libera |
use_color=1 |
color various notification elements - branch, user name etc. |
rev_prefix= |
text to prepend to commit IDs |
use_irc_notices=1 |
use notice instead of privmsg for notification messages |
squash_threshold=20 |
"squash" branch updates with more than said number of commits into a single notification |
pipeline_only_status= |
notify for pipeline events only for given status value; may be specified more than once. Available values seem to be success, failed, pending, and running. |
always_squash_branch=upstream&&always_squash_branch=upstream/master |
pushed of specified branch(es) will always be "squashed" into a single notification |
only_branch= |
notify for changes only on given branch; can be given more than once |
always_squash_outside_dir= |
squash commits touching files outside given directory; may be given more than once; squashed commits are presented in a single notification |
shorten_urls=1 |
shorten URLs using URL shortening service configured by instance's admin |
The bot supports all types of webhook events.
There are several ways to set the hook on salsa.debian.org: the web interface of a project, dpt-salsa (for the perl-team), salsa (in devscripts), a shell script to configure KGB via the Gitlab API from the postgres team, and probably other helpers.
Using IRC notifications with kgb-client
Cf. the generic KGB documentation at this wiki.