feat: Make webhook triggers configurable

[ctcanbol]

Currently for code reviews, the code reviewer workflow only triggered when the webhook trigger is review or bot specifically mentioned. If we want to also trigger it automatically when a PR opened (without selecting reviewer), we are no more allowed to (in previous versions, it can be done).

2026-05-27T14:06:20.442Z DEBUG 7 --- [AI Git Bot] [nio-8080-exec-3] o.r.giteabot.gitea.GiteaWebhookHandler : Unhandled Gitea PR action 'opened', ignoring

So my suggestion is; in settings page or somewhere appropriate, allow users to select or write which webhook triggers will trigger the PR bot to review the PR.

[tmseidel]

Hi @ctcanbol,
Have you tried the feature of CODEOWNERS? - This is a pattern, which is supported by Github, Gitea and Gitlab (even Bitbucket). If you assign the bot as Codeowner, it should be assigned as reviewer automatically. This should cover your requirement and gives you even more power to make a finer granulation on which files or folders the reviewer is assigned. It has also the adventage to keep more consistent regular git workflow and use more in-built-features of the git system instead of adding them on top in a slightly different form. I'd appreciate your feedback how this could resolve your issue. -> I'll move this item into the discussion section

[ctcanbol]

Thank you for the suggestion. I agree that the CODEOWNERS file is a powerful, built-in, and standard feature provided by Git systems. However, for our specific scenario, this approach unfortunately acts more as a workaround rather than a practical solution. The main reasons for this are:

• Operational Load on Existing Projects: We currently maintain hundreds of existing repositories. Having to go through and add a CODEOWNERS file one by one across all these projects just to assign the bot automatically would create a massive operational workload.

• New Projects and Template Management: For every new project created in the future, this file would need to be added manually, or we would have to update all of our existing project templates to accommodate this structure. This significantly increases maintenance overhead.

In summary, while CODEOWNERS is a great standard, having a parametric structure that can be configured centrally through the bot would be a much more scalable solution. I still believe that adding this capability directly to the bot would bring a very valuable and nice feature to the existing system.

[tmseidel]

@ctcanbol I've create issue #199