-
Bug
-
Resolution: Unresolved
-
Minor
-
None
We recently migrated from Bitbucket Server to GitHub and therefore changed the multibranch pipeline jobs of our projects. The migration just involved the exchange of Bitbucket branch source with GitHub branch source, we left the rest of the job configuration untouched. Everything works well so far but for some reason a push to a target branch like main does not trigger a build of all change requests with the same target. While working with Bitbucket we always saw new builds for branches that have the main branch as target when merging into main. That's expected behaviour as we configured the `Discover pull requests from origin` strategy to be `Merging the pull request with the current target branch revision` and this behaviour is also described in the docs. Does anyone know if there is more to it with this plugin or anything we can try to change?