GitLab provides a way to push update messages to an Irker server. When configured, pushes to a project trigger the service to send data directly to the Irker server.
See the project homepage for further information.
You first need an Irker daemon. You can download the Irker code from its repository:
git clone https://gitlab.com/esr/irker.git
Once you have downloaded the code, you can run the Python script named
This script is the gateway script, it acts both as an IRC client, for sending
messages to an IRC server obviously, and as a TCP server, for receiving messages
from the GitLab service.
If the Irker server runs on the same machine, you are done. If not, you need to follow the first steps of the next section.
- Navigate to the project you want to configure for notifications.
- Navigate to the Integrations page
- Click “Irker”.
- Ensure that the Active toggle is enabled.
- Enter the server host address where
irkerdruns (defaults to
localhost) in the
Server hostfield on the Web page
- Enter the server port of
irkerd(e.g. defaults to 6659) in the
Server portfield on the Web page.
- Optional: if
Default IRC URIis set, it has to be in the format
irc[s]://domain.nameand is prepended to each and every channel provided by the user which is not a full URI.
- Specify the recipients (e.g. #channel1, user1, etc.)
- Save or optionally click “Test Settings”.
Irker accepts channel names of the form
#chan, both for the
#chan channel. If you want to send messages in query, you need to add
,isnick after the channel name, in this form:
Aorimn,isnick. In this latter
Aorimn is treated as a nick and no more as a channel name.
Irker can also join password-protected channels. Users need to append
?key=thesecretpassword to the channel name. When using this feature remember to
not put the
# sign in front of the channel name; failing to do so
results in Irker joining a channel literally named
leaking the channel key through the
/whois IRC command (depending on IRC server
configuration). This is due to a long standing Irker bug.