Product
OVERVIEW
FEATURES
USE CASES
Case Studies
BUSINESS EDUCATION and RESEARCH OPEN SOURCE and COMMUNITIES
Resources
FOR USERS FOR ADMINISTRATORS
Pricing
Download
New organization
Log in
Sign up

Version control

GitLab

Version control

Back to list

Zulip GitLab integration

Receive GitLab notifications in Zulip!

  • Instructions for all platforms

  1. Create a bot for GitLab. Make sure that you select Incoming webhook as the Bot type.

  2. Decide where to send GitLab notifications, and generate the integration URL. You'll be able to configure which branches you'll receive notifications from.

  3. Go to your repository on GitLab and click Settings on the left sidebar. Click on Webhooks and select Add new webhook.

  4. Set URL to the URL you generated, and Name to a name of your choice, such as Zulip. Select the events you would like to receive notifications for, and click Add Webhook.

Note: If your GitLab server and your Zulip server are on a local network together, and you're running GitLab 10.5 or newer, you may need to enable GitLab's "Allow requests to the local network from hooks and services" setting (by default, recent GitLab versions refuse to post webhook events to servers on the local network). You can find this setting near the bottom of the GitLab "Settings" page in the "Admin area".

You're done! Your GitLab notifications may look like this:

Filtering incoming events

The GitLab integration supports filtering for the following events:

Push Hook, Tag Push Hook, Test Hook, Issue Hook open, Issue Hook close, Issue Hook reopen, Issue Hook update, Confidential Issue Hook open, Confidential Issue Hook close, Confidential Issue Hook reopen, Confidential Issue Hook update, Note Hook Commit, Note Hook MergeRequest, Note Hook Issue, Confidential Note Hook Issue, Note Hook DesignManagement::Design, Confidential Note Hook DesignManagement::Design, Note Hook Snippet, Merge Request Hook approved, Merge Request Hook unapproved, Merge Request Hook approval, Merge Request Hook unapproval, Merge Request Hook open, Merge Request Hook update, Merge Request Hook merge, Merge Request Hook close, Merge Request Hook reopen, Wiki Page Hook create, Wiki Page Hook update, Job Hook, Build Hook, Pipeline Hook, Release Hook, Feature Flag Hook, Resource Access Token Hook, Deployment Hook

Configuration options

  • By default, the Zulip topics for merge requests will contain the title of the GitLab merge request. You can change the topic format to just contain the merge request ID by adding &use_merge_request_title=false to the generated URL.

Logos are trademarks of their respective owners. None of the integrations on this page are created by, affiliated with, or supported by the companies represented by the logos.