As of #87, /open pr supports opening MSYS2-packages PRs also for msys2-runtime PRs. This is very different from the way /open pr is used otherwise, namely in component-updatesissues. As such, the, say, MSYS2-packages PR can be opened in a way that automatically closes such a corresponding component-updates issue, but the same is not true for the msys2-runtime PRs.
Alternatively, the msys2-runtime PR could be merged when the MSYS2-packages PR is merged, which is more in line with the manner component-update issues are automatically closed.
As of #87,
/open prsupports openingMSYS2-packagesPRs also formsys2-runtimePRs. This is very different from the way/open pris used otherwise, namely incomponent-updatesissues. As such, the, say,MSYS2-packagesPR can be opened in a way that automatically closes such a correspondingcomponent-updatesissue, but the same is not true for themsys2-runtimePRs.Let's close those
msys2-runtimePRs by "pushing" the PR branch (which in reality will look more like updating the default branch using the PR'shead.sha, like we already do to "merge"git-for-windows/gitrelease PRs).Alternatively, the
msys2-runtimePR could be merged when theMSYS2-packagesPR is merged, which is more in line with the mannercomponent-updateissues are automatically closed.