-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Check formatting early in CI #3711
Conversation
This commit makes formatting the first check, so that CI doesn't run for hours only to fail on style.
This makes changes to the formatter impossible to test. |
@BlaXpirit couldn't that be mitigated by simply running the formatter before pushing changes to the formatter? |
As an added bonus, reviewers would get to see what the changes look like practice. |
@andrewhamon, that is indeed what people do, but with this change the check will run the old formatter (before recompilation with new source) and conclude that there are differences in the result. Basically, any changes to formatter will always make this fail. Overall I like the sentiment. I had the exact same idea, but realized that it's not so easy to do... |
I see now 😅 My apologies. So I know very little about the build process... but could things be arranged like so:
Also, why does |
@andrewhamon there are some things about the bootstrapping process that complicate everything (add some unusual constraints). Perhaps newer standard library must always still work on older compiler, or something like that. As I understand it: |
Hmmm... well this really isn't a huge deal or anything, but it would help when noobs like me come along and forget to format. The CI wait times are brutal. I'm going to close this since its not super important to me and I'm about to be offline for the next few days. |
|
This commit makes formatting the first check, so that CI doesn't run for
hours only to fail on style.