Why are 2 PRs needed to trigger this?

[robandpdx]

I am working in a repo that has branch protection on the development branch and all release/**/* branches. So change to release/0.1.0 must happen via a PR. In order to tigger the cascading merge, I would also need to open a PR from release/0.1.0 to development after my initial PR into release/0.1.0 is merged.

Bitbuckets' Automatic branch merging does not require this second PR to development. Why is this needed? Is there a way to configure this so that the cascading merge will trigger on any merge to any of the release/**/* branches?

Maybe I'm missing something.

[robandpdx]

I found that the cascading merge functions as I expect, without the need to create a PR into development if I exclude the following from the workflow:

    if: |
      github.event.pull_request.merged == true &&
      startsWith(github.head_ref, 'release/')

Or better yet, change the if condition to require that the PR is into a release/* branch, rather than from a release/* branch, as follows:

    if: |
      github.event.pull_request.merged == true &&
      startsWith(github.base_ref, 'release/')

With this configuration, the workflow behaves exactly like Bitbuckets' Automatic branch merging, where the merge to the development branch is the final merge in the sequence.

Should the README be updated to show people how to get this to behave exactly like Bitbuckets' Automatic branch merging?