We have a workflow where we merge our release branch back into our master branch periodically. To do this, we create a PR that merges the release branch back to master. Our configuration is setup to use the "Exclude branches that are also filed as PRs" branch discovery strategy, but it builds these "branch"-type status checks for these kind of "merge release by back to master" PRs anyway. I believe it's because the commit in the PR is in a branch that's in the include filter (the release branch): "release/*" (matches our release branches) is in the include filter.

Ideally, PRs wouldn't build trigger this extra build, which is typically only run a commit lands on the release branch.