Webhooks limit configuration per project on Gitlab SaaS
Proposal
Currently Gitlab SaaS doesn't provide any way to configure Webhooks limit per project (defaults to 100). Configuration is possible for self-hosted Gitlab instance, but only on a global instance level.
As a premium client that use Gitlab extensively, we have faced this as a critical limitation on one of our monorepos that triggers deployments on AWS Amplify via project webhooks. Unfortunately, webhooks are managed by AWS Amplify via Gitlab API and depend on amount of applications hosted in Gitlab repository. We have exhausted this limit, and due to this cannot add new application to monorepo anymore. This blocks us and forces to consider monorepo split, but such change will come at a big cost for our business. We believe that feature with configurable webhooks limit per project/group could be valuable not only for our case, but for other companies that use monorepos together with integration of third-party tooling.