You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
As of #87,
/open pr
supports openingMSYS2-packages
PRs also formsys2-runtime
PRs. This is very different from the way/open pr
is used otherwise, namely incomponent-updates
issues. As such, the, say,MSYS2-packages
PR can be opened in a way that automatically closes such a correspondingcomponent-updates
issue, but the same is not true for themsys2-runtime
PRs.Let's close those
msys2-runtime
PRs 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/git
release PRs).Alternatively, the
msys2-runtime
PR could be merged when theMSYS2-packages
PR is merged, which is more in line with the mannercomponent-update
issues are automatically closed.The text was updated successfully, but these errors were encountered: