There are PRs which state in Gitea: "This pull request has changes conflicting with the target branch."

As for all PRs also for these PRs the Gitea webhooks Jenkins and the build fails as expected. See attached log for the thrown exception.

Additionally there is no possibility to catch the exception, since it is thrown within the default checkout stage and so there is no possibility to handle it better, e.g. by means of  build failure analyzer or a meaningful notification.

Expected Results: Gitea does not trigger/webhook pull requests which have changes conflicting with the target branch. Or the Jenkins Gitea Plugin do recognize such webhooks and does not start a build. Both alternatives could be configurable.

Maybe the API flag "mergeable" should be considered?