A special pipeline which only runs on pull requests. Pull-requests has the same level of indentation as branches .
This type of pipeline runs a little differently to other pipelines. When it’s triggered, we’ll merge the destination branch into your working branch before it runs. If the merge fails we will stop the pipeline.
You’re right, Bitbucket Pipelines folks have implemented proper support of PR build. Still we won’t develop issue reporting as comments in the PR. Even if it was our original strategy in GitHub and Azure Devops, we are moving away from it, since it has a lot of drawbacks. In short, comments are for humans, not for bots.
On GitHub, they have recently added the GitHub Checks feature, that is specifically designed for automated tools to report issues on PR. We moved to it.
On Bitbucket Server, they have the Code Insight feature, and we just released our integration.
Regarding Bitbucket Cloud, we have started discussion with Atlassian, and even if I can’t share any precise information, I feel they will sooner or later propose a similar feature. But as of today they don’t have a specific way for automated tools to report annotations on the code. And since we don’t want to hack comments, then we are not planning to move on this topic.