Hi Chris,
GitHub does expose refs/pull/
– currently these branches don’t get updated until somebody actually went to the PR page or requests a PR information via REST or GraphQL API;
– GitHub states that this is only an internally functionality, that is not guaranteed to be working in the future.
For these reasons Pull Requests plugin doesn’t support these branches. You can of course always configure your branch specs (e.g. refs/(pull/*/merge)
) to match them, but this way you will not be using the Pull Request build feature functionality, such as showing PR information in TeamCity UI and no filtering of any kind (i.e. by target branch or author’s role) will be applied.