PR trigger not working when target branch changes

[benedikt.viebahn]

Bitrise Build Issue Report template

Description of the issue

I already found these 2 old issues, but no solutions:

Automatically re-build open pull request when target branch is updated (e.g. another Pull Request is merged)

From @jhassine on Fri Oct 07 2016 09:23:45 GMT-0400 (EDT) If you have a branch, e.g. master, which is the target of the PRs, then any change on master should trigger a new build for every open PRs. Use case: you have 5 open Pull Requests you merge a Pull Request the remaining 4 open Pull Requests should be re-tested, for a refreshed Pull Request status (allow/don’t allow merge) But in general, if e.g. master changes (even if by a code push directly on master) every open Pull Request should …

Trigger PR builds from master merge

Is it possible to kick off all outstanding open PR builds whenever a merge to master occurs? I can’t quite see how I would achieve that with the current triggers. I’d like a PR build to occur not when there’s a specific PR criteria but when a merge to master happens?

I’m a bit confused why there was no activities on these issues, since this seems like a pretty bad bug to me. There is a linked GitHub issue in one of them, but it doesn’t exist anymore, so I don’t know what was discussed there.

I’ll explain again, but the problem is exactly the same as in the mentioned issues: have a workflow that is triggered by pull requests:

trigger_map:
- pull_request_source_branch: '*'
  workflow: test
- pull_request_target_branch: '*'
  workflow: test

When the source branch of a PR is updated, the workflow reruns as expected. However, when the target branch of a PR is updated, for example because a different PR was merged, the workflow doesn’t run again on the remaining PRs.