This would replace something annoying for senior developers by something annoying for new contributors. I'm not sure if this is a good idea.
Did you have to manually resolve merge conflicts in your example? If not, just don't push it back to the repository in such a situation in the future. If so, I agree with Tobias that *needs review* is a correct status. Kwankyu Lee schrieb am Montag, 5. August 2024 um 12:50:53 UTC+2: > But more importantly, if we disable this action, it would be a regression > for developers who cannot set labels themselves. > > > Isn't it enough to add "needs review" label only when draft PR is > converted to a non-draft PR? Those developers may control the draft status. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0362e752-9290-44c7-bfdc-1bc652d5b719n%40googlegroups.com.
