<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=3003) </details> <!--IssueSummary end--> ### Description When a new project is created in a group (or on the system), there is no way to know that this event happened to be able to react to it by receiving a webhook. ### Proposal Add a new event type in the list of webhooks event on a group page that would send Project events for the following cases: - Project created - Project deleted - Project renamed - Project transferred  ### Links / references I'm not sure what the code at the following line does but it would probably be the good place to send the event if this is not what is already being done: https://gitlab.com/gitlab-org/gitlab-ce/blob/810866ecb6c7be4fdac88dc3b2a6cd9ad49ac7bf/app/services/projects/create_service.rb#L96 ### Documentation blurb #### Overview Automate configurations and tasks based on the projects events listed above. #### Use cases The reason behind it is to be able to setup the repository with some file and automatically create a Jenkins job to build this repository. Templates mitigate this issue for project using Gitlab CI, but even then, it's not an automated process that could setup other files than the .gitlab-ci.yml. ### Feature checklist Make sure these are completed before closing the issue, with a link to the relevant commit. - [ ] [Feature assurance](https://about.gitlab.com/handbook/product/#feature-assurance) - [ ] Documentation - [ ] Added to [features.yml](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/features.yml)