summaryrefslogtreecommitdiff
path: root/doc/user/project/integrations/irker.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/integrations/irker.md')
-rw-r--r--doc/user/project/integrations/irker.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/user/project/integrations/irker.md b/doc/user/project/integrations/irker.md
index bb4a5b2b97f..8dd7e4309b4 100644
--- a/doc/user/project/integrations/irker.md
+++ b/doc/user/project/integrations/irker.md
@@ -1,20 +1,20 @@
---
stage: Create
group: Ecosystem
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Irker IRC Gateway
GitLab provides a way to push update messages to an Irker server. When
-configured, pushes to a project will trigger the service to send data directly
+configured, pushes to a project trigger the service to send data directly
to the Irker server.
See the project homepage for further information: <https://gitlab.com/esr/irker>
## Needed setup
-You will first need an Irker daemon. You can download the Irker code
+You first need an Irker daemon. You can download the Irker code
[from its repository](https://gitlab.com/esr/irker):
```shell
@@ -26,8 +26,8 @@ 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 will
-need to follow the firsts steps of the next section.
+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.
## Complete these steps in GitLab
@@ -40,7 +40,7 @@ need to follow the firsts steps of the next section.
1. Enter the server port of `irkerd` (e.g. defaults to 6659) in the
`Server port` field on the Web page.
1. Optional: if `Default IRC URI` is set, it has to be in the format
- `irc[s]://domain.name` and will be prepend to each and every channel provided
+ `irc[s]://domain.name` and is prepended to each and every channel provided
by the user which is not a full URI.
1. Specify the recipients (e.g. #channel1, user1, etc.)
1. Save or optionally click "Test Settings".
@@ -48,13 +48,13 @@ need to follow the firsts steps of the next section.
## Note on Irker recipients
Irker accepts channel names of the form `chan` and `#chan`, both for the
-`#chan` channel. If you want to send messages in query, you will need to add
+`#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
case, `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 will
-result on Irker joining a channel literally named `#chan?key=password` henceforth
+**not** put the `#` sign in front of the channel name; failing to do so
+results in Irker joining a channel literally named `#chan?key=password` henceforth
leaking the channel key through the `/whois` IRC command (depending on IRC server
configuration). This is due to a long standing Irker bug.