-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: enforce formatting #741
Conversation
Could anyone please approve workflow, just for the purpose of seeing it fail? |
ffb56ba
to
4cc957d
Compare
Rebased. Please approve workflow and review. |
Oh, and we did confirm enforcement works (the first commit) in this run. |
Unsurprisingly, the checks passed. There is no good time to merge this. It may upset contributors with open pull requests. There are 40 open pull requests. Yet, that number might not decrease. Therefore, it may never be less painful than now to merge this. And it's only a click away! 😉 |
@mightyiam There was a recent important discussion about enforcing formatting anyway in #702 (that and more...). I guess it's currently delayed the time to try to implement some RFC. |
Thanks. Let us know here, as soon as we can pull the trigger on this. The first commit is the enforcement part. The second is merely the result of |
#744 bumped actions/checkout to v4, I guess you might want to do the same. |
Thank you. Done. |
Thank you! I'm closing this in favor of #751 (which is just a replay of the commits), for reasons explained there. |
No description provided.