Pipelines for any GitLab API event

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Problem to solve

It's great that we're extending pipelines to be triggered by merge request creation and update rather than just branch creation and update, but there's a slew of other events that should be able to trigger CI/CD pipelines.

Target audience

Developers, Operations, Project Managers.

Further details

We could, for example, let someone trigger CI/CD pipelines when issues are created, or a label is added to a MR, or a user is added to a group, or really, anything GitLab is aware of. Heck, perhaps even external triggers (although we already have APIs directly for that, but maybe we should let you specify other external systems to poll or register with, like Docker Hub image update).

This will be particularly valuable if/when we support multiple distinct pipelines so that each type of even can be conceptualized separately, but it still has value without that.

Proposal

What does success look like, and how can we measure that?

Links / references

  • See GitHub Actions
Edited Sep 04, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading