Hi. sure it is a clean runner from docker image. Checkout is done via GitLab. Also we had no such problem before, it has appear around 1 month ago without any changes from out side. Appears quite often but at same time not always.
I would be checking our CI pipelines, but we see 2 weeks old master changes in recently created PR. So these changes were analyzed in master 2 weeks ago and still pops out in coverage report.
I don’t want to remove “pre-merge” with git merge origin/${BITBUCKET_PR_DESTINATION_BRANCH}
since it provides additional check for merge compatibility with target branch.
It is not really a hybrid it is an update to PR target branch ( in most cases it is just master branch and master changes are already analyzed)
Also it is a default behavior for Bitbucket Pipelines for PRs. So it should be supported.
pull requests
A special pipeline that only runs on pull requests initiated from within your repository.
It merges the destination branch into your working branch before it runs.
Pull requests from a forked repository don't trigger the pipeline. If the merge fails, the pipeline stops.