-
Notifications
You must be signed in to change notification settings - Fork 449
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
Move linting checks to start of CI run #1059
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1059 +/- ##
==========================================
+ Coverage 78.75% 78.79% +0.04%
==========================================
Files 248 248
Lines 9371 9371
==========================================
+ Hits 7380 7384 +4
+ Misses 1991 1987 -4
Continue to review full report at Codecov.
|
#### stage: lint | ||
# | ||
# Note: For all of these lints we `allow_failure` so that the rest of the build can | ||
# continue running despite them not passing. Merging is still disallowed since (most) of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as an FYI: I checked and it's only spellcheck
which is currently not required for merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try it out.
* Move linting checks to start of CI run * Test RustFmt failure * Test Clippy quickfail * Try adding `allow_failure` to Clippy jobs * Allow lint steps to fail in the GitLab CI * Revert test failures in `flipper`
It's really annoying to wait half an hour while the CI does its job, only to realize that
you forgot to run
rustfmt
and now you have to wait another half an hour for the CI topass.
This PR moves our linting steps to the beginning of the CI pipeline so that these
failures can be caught and addressed quickly.
This PR also allows the CI build to continue despite the lint steps failing. This is
useful if you care about a step later in the CI pipeline (e.g contract sizes) but don't
necessarily care if your code is formatted properly.