I simply cannot believe that such an obvious use case is not possible, which is to have the Pipeline be triggered when a Pull request is performed against a specific branch.

How should I do a pull request through multiple branches from different repositories? Do I need to do the fork for all of my repos and add them into a project, and see if it works or not?

This feature seems to work very well within a repository, but not when you open a pull request from a fork back to the main repo. Does that count as a separate feature (see Aneita Yang’s sticky post re: ‘if this doesn’t do what you want, open an issue', or would it be a dupe of [pipelines for pull requests from forks|BCLOUD-13162%3F_ga%3D2.128772748.1000000455.1560536725-29546397.1531695922]?)

If you want to run regardless of destination I suppose the current setup is fine, but do you care about the source at all? I.e. would using a wildcard in a reverse setup work the same for your use case?

You could check destination in a script if that fits your use case, I guess. For our use case, we want PRs to run pipeline regardless of destination.

to make sure merged PRs won't break.

Sure, but even then I only care about merges to specific branches, so the way I see it triggering based on source is just a waste of build minutes.

I fail to see a usecase for the PR pipelines in their current form

I think the biggest use case is to run tests to make sure merged PRs won't break. And that's a pretty big use case (hence the most voted issue on here).

I can see your use case for destination based pipeline as well, for deployment purposes. Glad to see an issue created for that

@joakimhedlunddanielwellington

I just saw your comment. I agree :100:%

A few days before your comment I actually made an issue / feature request for having pull-request triggers for pipelines based on destination branch:

BCLOUD-17859

Please add your input there as well so we can get more people involved in making this reques a priority for
Atlassian / @gcrain / @davinaaa

Thanks for getting back to me @gcrain

I would argue that the deployment strategy should be left to the user to decide on. However, I fail to see a usecase for the PR pipelines in their current form. Could you provide an example of how they're meant to be used?

Hi @joakimhedlunddanielwellington,

the branch pattern under pull requests defines the source branch. This is so that you can run a different pipeline depending on the fix. For example you may have a different set of tests for feature branches vs hotfix branches. Note that this is only talking about the tests that run against the PR during development.

In the case you describe, it sounds like you just want a branch build against master. Or rather, you don't want to deploy to staging from a PR / feature branch - this would break as soon as you have a second PR opened.

Hope this helps

Cheers,
Geoff