MergeMe logoMergeMe
Published on

GitLab Slack push notifications: Fix missing commit alerts

Authors
  • Name
    Maruan

To fix missing GitLab Slack push notifications, open Settings > Integrations > GitLab for Slack app, tick the Push event, enter a Slack channel for that event, save, and then verify with a real push from a permitted branch. If the Push trigger is off, or its channel field is empty or wrong, the native app has nowhere to send commit alerts, even when the connection looks healthy.

This guide covers only the native GitLab for Slack app on GitLab.com or self-managed GitLab. It is not an install walkthrough and it is not a pipeline-alert guide. It separates the four triggers people mix up (Push, Tag push, Pipeline and Merge request), shows how to check the channel and private-channel membership, and gives you a safe way to prove delivery instead of guessing.

The short fix: enable Push, set its channel, save, verify

The fix is four moves, in this order. Skipping the channel step is the most common reason a ticked box still produces silence.

  • Open the project, then go to Settings > Integrations > GitLab for Slack app.

  • Select the Push event checkbox.

  • Enter the Slack channel for that event. GitLab asks for channels per event, and you can enter up to ten comma-separated channel names.

  • Save changes, then verify with a real push (covered below).

The settings page also offers a Test settings option. Use it, but a pass isn't proof that commit alerts work. It tells you the integration can talk to Slack. It doesn't tell you that a push to your repository will land in the channel you typed.

If the Push box was already ticked and alerts are still missing, it's almost always one of three things: the wrong trigger for what you expected, a channel that is blank or mistyped, or a private channel the app was never added to. The next sections take those in turn.

Where do I install the GitLab for Slack app in project settings?

In your project, go to Settings, then Integrations, and open GitLab for Slack app. Select Install GitLab for Slack app, pick the Slack workspace, and approve the permissions on the Slack authorization screen. After you return to GitLab, tick the Push events trigger and fill its channel field. The exact menu labels can shift between GitLab versions, so check GitLab's own documentation for your release.

Push, Tag push, Pipeline and Merge request: which trigger sends what

Each trigger answers a different question, and ticking the wrong one is why people think the app is broken. The documented meanings are short:

  • Push: a push was made to the repository. This is the commit alert most people mean when they say "commit notifications".

  • Tag push: a tag was pushed or removed. A release tag won't fire Push, and a normal commit won't fire Tag push.

  • Pipeline: a pipeline status changed. This is CI state, not code arriving. A push can start a pipeline, but the Pipeline notification reports the pipeline's status, not the commit.

  • Merge request: activity on a merge request, such as opening or merging one.

The decision rule is simple. If you want to know that code landed, use Push. If you want to know a release was tagged, use Tag push. If you want green or red build status, use Pipeline. If you want review lifecycle, use Merge request.

Each trigger carries its own channel field, so you can send Push to one channel and Pipeline to another. That is also how alerts end up in the wrong place: a channel entered under Pipeline does nothing for Push. For pipeline filters and a test routine, see GitLab Slack failed pipeline notifications: setup and test instead of repeating that setup here.

Check the channel field and private-channel membership

If alerts are still missing after you've picked the right trigger, the problem is the channel, not the checkbox. Check two things.

First, read the channel field for the Push event character by character. Channel names go in per event, comma-separated, up to ten. A typo, a renamed channel or a stray entry under the wrong event leaves Push with no valid destination.

Second, if the destination is a private channel, the app must be a member. GitLab's documented step is to add it from inside that channel: type @GitLab and choose Add to Channel. Until that happens, a private channel won't receive notifications, and the GitLab settings page gives no warning.

A quick way to separate the two causes: temporarily point Push at a public channel you can see. If alerts arrive there, your trigger and connection are fine and the original channel is the problem. If they still don't arrive, go back to the trigger and the verification step below.

If the whole app connection looks wrong rather than one channel, the related runbook on GitLab Slack notifications after token rotation is a better starting point.

Prove delivery with a real push on a disposable branch

Verify with the event itself, not with a settings-page test. A real push is the only check that exercises the Push trigger end to end.

Do it safely:

  • Create a disposable branch that your team's normal policy lets you push to.

  • Make a harmless commit, such as a whitespace change in a scratch file.

  • Push it, then watch the channel you set for Push.

  • Delete the branch afterwards.

Don't change the default branch, branch protection or CI settings just to run this test. If your rules block pushes to the branch you chose, use a branch they allow rather than loosening anything.

Read the result like this. The alert appears: Push works, and any earlier gap was the channel or private-channel membership. Nothing appears in the Push channel but a pipeline alert does: you ticked Pipeline and not Push, or the Push channel is wrong. Nothing at all appears: recheck that you saved, that the channel field holds a valid name, and that the app is in the private channel.

Test one trigger at a time. Pushing a tag while you're also watching Push muddies the result, because Tag push is a separate event.

Branch and inherited settings: what is documented and what to observe yourself

The settings page includes a branch dropdown, and it's tempting to assume it simply filters Push alerts. Treat that as unconfirmed. The documentation names the control.

So observe it instead of assuming it. Run your disposable-branch test twice: once on a branch the dropdown should include, once on a branch it should not. Note which alerts arrive for each. Two pushes show you your instance's real behavior, without relying on a rule nobody has documented for you.

The same caution applies to settings that might be inherited from a group or instance. Where the official page documents inheritance, follow it. Where it doesn't, check the project's own Integrations page first, and compare what you see there with what you expect from the group. If a project-level value looks right but alerts still behave oddly, an inherited setting is a reasonable suspect, and your observation test will confirm it.

For the other side of branch handling, see the guide on GitHub Slack branch filters, which takes the same "test it, don't assume it" approach.

When native push alerts are the wrong tool for review visibility

Native Push alerts tell you code arrived. They don't tell you whether anyone is reviewing it. If your real complaint is "merge requests sit unnoticed", more commit alerts will make it worse, because every push becomes another message in the channel.

That's when to stop tuning Push and look at review visibility. MergeMe shows each GitHub pull request and GitLab merge request in Slack as one card that updates in place, and it connects GitHub.com, GitLab.com and self-hosted GitLab in one workspace. It doesn't replace the Push trigger, and this post doesn't suggest it forwards push events. It answers a different need: seeing the state of each merge request in one place instead of reading a stream.

Two posts help you decide. GitLab Slack slash commands vs notifications explains what the native app does through commands versus alerts, and GitLab Slack test works but merge request notifications missing covers the merge request side of the same trigger confusion.

Fix the trigger first, then decide if you need review cards

Most missing GitLab Slack push notifications come down to one unticked Push box, an empty or wrong channel, or a private channel the app never joined. A real push on a disposable branch tells you which. If commit alerts work but merge requests still go unseen, try MergeMe's free Hobby plan and see each merge request as one updating card in Slack.

FAQs

Why am I not getting GitLab Slack push notifications?

Usually the Push event is not ticked, its channel field is empty or wrong, or the destination is a private channel the app was not added to. Enable Push, enter its channel, save, and verify with a real push on a permitted disposable branch rather than relying on the Test settings button.

What is the difference between Push and Tag push in GitLab for Slack?

Push fires when a push is made to the repository, which covers normal commits. Tag push fires when a tag is pushed or removed. Pipeline reports a pipeline status change and Merge request reports merge request activity. Each trigger has its own channel field, so set the one you actually want.

How do I send GitLab Slack notifications to a private channel?

Add the GitLab for Slack app to that channel by typing @GitLab inside it and choosing Add to Channel. Then enter the channel name under the event you want, save, and test with a real push. Without membership, the private channel will not receive the alerts.

Does the Test settings button prove push notifications work?

No. It checks the integration settings, not delivery of a real push event. To prove Push works, make a harmless commit on a disposable branch you are allowed to push to and watch the channel you set for Push. Do not alter protected branches or CI settings to run the test.

Can MergeMe replace GitLab Slack push notifications?

No. MergeMe does not forward push events. It shows each GitHub pull request and GitLab merge request in Slack as one updating card, across GitHub.com, GitLab.com and self-hosted GitLab. Use the native Push trigger for commit alerts and MergeMe when your goal is clearer merge request visibility.