Allow group level webhooks to apply recursivly

Description

Webhooks configured on a group should apply (optionally?) recursively below the group that has the hook configured. If I configure a hook on a group the natural (to me at least) behavior would be for child groups and projects to inherit this hook, ex: Parent group has a webhook configured for push events, then I would expect to get push events for any project that is in the parent groups child tree.

Proposal

  • Possibly add an option to hooks configured on a group that would govern the hooks recursive nature.
  • When looking for hooks to execute for an action, check parent groups for hooks that applies to the current action.

Links / references

Documentation blurb

Overview

Use cases

The generic use case would be to simplify administration of any group that uses subgroups.

My specific use case is that we have around 300 projects in a tree structure and would like to have events for these sent to a central message bus for further use in the company. The goal would be to configure the top level group(s) with the desired webhooks and the it would just work, regardless if new projects or sub groups are added.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

Edited by 🤖 GitLab Bot 🤖