Action switches to wrong ref when creating PR with same source branch to 2 different target branches

[M-arcus]

I have 3 branches:

• main (current production state)
• update (branch for basic package update from renovate)
• development (current staging state)

Now I created 2 PRs to merge a package update into both branches:

• update -> development (PR 924)
• update -> main (PR 925)

The Github Action Code Style Checks for PR 925 (see screenshot "backend", triggered by on:pull_request) switches to the ref for PR 924 and then fails because there are issues. My action runs for main now fail because of an issue on development.

Why does it pull the ref for PR 924 ? Shouldn't it pull 'refs/remotes/pull/925/merge' instead of 'refs/remotes/pull/924/merge'?