Skip to content

Commit cbe4de2

Browse files
committed
Book: Add continuous integration description
1 parent 6b21d38 commit cbe4de2

File tree

2 files changed

+17
-1
lines changed

2 files changed

+17
-1
lines changed

book/src/SUMMARY.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
- [Configuration](configuration.md)
88
- [Clippy's Lints](lints.md)
99
- [Continuous Integration](continuous_integration/README.md)
10-
- [Travis CI](continuous_integration/travis.md)
1110
- [GitHub Actions](continuous_integration/github_actions.md)
11+
- [Travis CI](continuous_integration/travis.md)
1212
- [Development](development/README.md)
1313
- [Basics](development/basics.md)
1414
- [Adding Lints](development/adding_lints.md)
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,17 @@
11
# Continuous Integration
2+
3+
It is recommended to run Clippy on CI, preferably with `-Dwarnings`, so that
4+
Clippy lints prevent CI from passing.
5+
6+
We recommend to use Clippy from the same toolchain, that you use for compiling
7+
your crate for maximum compatibility. E.g. if your crate is compiled with the
8+
`stable` toolchain, you should also use `stable` Clippy.
9+
10+
> _Note:_ New Clippy lints are first added to the `nightly` toolchain. If you
11+
> want to help with improving Clippy and have CI resources left, please consider
12+
> adding a `nightly` Clippy check to your CI and report problems like false
13+
> positives back to us. With that we can fix bugs early, before they can get to
14+
> stable.
15+
16+
This chapter will give an overview on how to use Clippy on different popular CI
17+
providers.

0 commit comments

Comments
 (0)