I have a private repo that a developer created a private fork of. When they created a PR the pipeline didn't run and no code quality metrics ran agains it. I'm curious if this is normal or if the pipeline should run agains a submitted PR?
Seems like this scenario in GitHub would run the Workflow agains the PR so I know if its a quality (test / lint / sonar / etc).
I think the answer to this is **no** which is a huge same. The reasons the triggers run agains a source branch not the destination branch. In the case of a source branch is part of a different repository.
This is a huge problem because you can't run code quality / tests **before** you merge. This makes forking on bitbucket useless.
Oh Bitbucket 🤷
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events