On Friday, January 31, 2025 at 2:44:39 AM UTC+9 dim...@gmail.com wrote: You can just check whether CI failures are relevant to your branch, and if not, write so in comments.
I think we should adopt a policy that promptly (no excuse) disable any CI check that fails due to reasons unrelated to a PR. Disable and enabling a workflow (CI check) may be done through PRs as well. The current practice ignoring erroneous CI checks is degrading the quality of developer life. -- 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 visit https://groups.google.com/d/msgid/sage-devel/0d834ad7-a51a-4bd6-ac1c-f4dc5acbd6edn%40googlegroups.com.
