@@ -23,6 +23,7 @@ All contributors are expected to follow the [Rust Code of Conduct](http://www.ru
23
23
* [ How Clippy works] ( #how-clippy-works )
24
24
* [ Fixing nightly build failures] ( #fixing-build-failures-caused-by-rust )
25
25
* [ Issue and PR Triage] ( #issue-and-pr-triage )
26
+ * [ Bors and Homu] ( #bors-and-homu )
26
27
* [ Contributions] ( #contributions )
27
28
28
29
## Getting started
@@ -257,6 +258,17 @@ Our highest priority is fixing [crashes][l-crash] and [bugs][l-bug]. We don't
257
258
want Clippy to crash on your code and we want it to be as reliable as the
258
259
suggestions from Rust compiler errors.
259
260
261
+ ## Bors and Homu
262
+
263
+ We use a bot powered by [ Homu] [ homu ] to help automate testing and landing of pull
264
+ requests in Clippy. The bot's username is @bors .
265
+
266
+ You can find the Clippy bors queue [ here] [ homu_queue ] .
267
+
268
+ If you have @bors permissions, you can find an overview of the available
269
+ commands [ here] [ homu_instructions ] .
270
+
271
+
260
272
## Contributions
261
273
262
274
Contributions to Clippy should be made in the form of GitHub pull requests. Each pull request will
@@ -288,3 +300,6 @@ or the [MIT](http://opensource.org/licenses/MIT) license.
288
300
[ triage ] : https://forge.rust-lang.org/triage-procedure.html
289
301
[ l-crash ] : https://github.com/rust-lang/rust-clippy/labels/L-crash%20%3Aboom%3A
290
302
[ l-bug ] : https://github.com/rust-lang/rust-clippy/labels/L-bug%20%3Abeetle%3A
303
+ [ homu ] : https://github.com/servo/homu
304
+ [ homu_instructions ] : https://buildbot2.rust-lang.org/homu/
305
+ [ homu_queue ] : https://buildbot2.rust-lang.org/homu/queue/clippy
0 commit comments