-
Joined on
2023年09月10日
maybe have Testing auto-generated by CI from all the feature branches? it'd have to exclude PRs from forks unless you have an allowlist. it'll also need to exclude those with merge conflicts.
apparently v4 has been released on the main package, so this issue is a whole lot less important now. still leaving it open for if/when v5 branches.
the PR I ran into this on is my own PR that I marked for merging, then CI failed, so I force pushed a few times but it then unexpectedly merged once CI passed once. so dismissing approvals seems...
they fixed it in f0be37ce3c which is only included in 5.16.1 but not in any branches.
I ran into this same problem myself, I agree this is a critical flaw that should be fixed or at least let us disable auto-merge for an entire forgejo instance.
I verified that 5.16.1 fixed the bug.
looks like this may be fixed at least partially in 5.16.1: https://github.com/luanti-org/luanti/issues/17161
Ok, I had assumed it was in English because I remember the other screenshots being all in English. Sorry for the confusion.
exchangeclone is effectively dead, my PR was never merged