Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Find a better way for handling mergify #641
Currently, there is a mergify rule that checks for a selected checkbox with the label Ready to merge to actually trigger the automatic merging:
I'd consider this to be a hack around the way it is supposed to work and would like to find a way on how we not have to rely on this.
As far as I understand, the problem is that without a label "work-in-progress", mergify will just merge as soon as the PR is approved, even though the owner might still have some work locally that they would want to include.
Let's discuss other ways on how we can prevent this from happening :)
If we do a label, it would be convenient to have one that starts with a letter early in the alphabet so that is listed right at the top. Suggestions:
@comit-network/rust-devs opinions? :)