Skip to content

No webhook sent when more than one tag is pushed at once

Summary

Tag push events webhook is not triggered when a push includes multiple tags.

Steps to reproduce

  1. Set up some kind of web service which can receive and record POST requests.
  2. In a self-hosted gitlab instance
  3. Configure a system webhook to trigger only on tag push events.
  4. Create a repository with some commits.
  5. Make a new commit. Put more than one tag on it: git tag -sm test1 test1, git tag -sm test2 test2
  6. git push --follow-tags to push the new commit and both new tags at once.

What is the current bug behavior?

No webhooks are sent at all.

What is the expected correct behavior?

A webhook should be sent for each tag, or some sort of combined webhook.

Relevant logs and/or screenshots

git push output, here there are four new tags, and the webhook did not trigger for any of them. The webhook works fine for pushes including one new tag and new commit(s).

Enumerating objects: 108, done.
Counting objects: 100% (102/102), done.
Delta compression using up to 16 threads
Compressing objects: 100% (44/44), done.
Writing objects: 100% (92/92), 20.31 KiB | 10.15 MiB/s, done.
Total 92 (delta 60), reused 74 (delta 48), pack-reused 0 (from 0)
To salsa.debian.org:emacsen-team/org-make-toc.git
   3fe8dce..bf9bb71  master -> master
 * [new tag]         v0.6 -> v0.6
 * [new tag]         debian/0.6-1 -> debian/0.6-1
 * [new tag]         0.6 -> 0.6
 * [new tag]         test -> test

Here is the webhook configuration:

screenshot

GitLab environment

This is happening for me on Debian's gitlab instance, salsa.debian.org. Salsa is running:

GitLab Community Edition v17.11.6.

I'm not the gitlab administrator; I'm an operator of the service which is the webhook target and is receiving the unwanted events.

Edited by 🤖 GitLab Bot 🤖