Gearset recently updated its automated webhook setup for new CI/CD jobs to use a shared webhook. For my team, we have configured each webhook for validation jobs to only run on PR creation/update and deployments to only run on branch pushes. By forcing the new jobs to a single shared job, it causes PR merges to trigger validations alongside the deployment (Which is time-consuming and needless).

Also, as my team has many legacy webhooks for our existing jobs, when we add a new job it seems Gearset randomly assigns it to an existing webhook. For our recent deployment-only job, it was connected to a validation job's webhook and would never run on merging PRs to that branch.

I received interim support to help configure the webhook manually for the new job, but am requesting the UI to be updated to allow me to choose between a shared existing webhook and to create a new webhook in BitBucket.