From 1ad322236dbe54ada2c284bda4a2b72830b3ff3d Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Wed, 20 Mar 2019 15:34:09 +0300 Subject: [PATCH] remove old contributing --- docs/dev/CONTRIBUTING.md | 18 ------------------ docs/dev/README.md | 6 ++++++ 2 files changed, 6 insertions(+), 18 deletions(-) delete mode 100644 docs/dev/CONTRIBUTING.md diff --git a/docs/dev/CONTRIBUTING.md b/docs/dev/CONTRIBUTING.md deleted file mode 100644 index a2efc7afa5..0000000000 --- a/docs/dev/CONTRIBUTING.md +++ /dev/null @@ -1,18 +0,0 @@ -The project is in its early stages: contributions are welcome and would be -**very** helpful, but the project is not _yet_ optimized for contribution. -Moreover, it is doubly experimental, so there's no guarantee that any work here -would reach production. - -To get an idea of how rust-analyzer works, take a look at the [ARCHITECTURE.md](./ARCHITECTURE.md) -document. - -Useful labels on the issue tracker: - * [E-mentor](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-mentor) - issues have links to the code in question and tests, - * [E-easy](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy), - [E-medium](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-medium), - [E-hard](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-hard), - labels are *estimates* for how hard would be to write a fix. - -There's no formal PR check list: everything that passes CI (we use [bors](https://bors.tech/)) is valid, -but it's a good idea to write nice commit messages, test code thoroughly, maintain consistent style, etc. diff --git a/docs/dev/README.md b/docs/dev/README.md index 74bf86f68a..0c09dddfc9 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -35,3 +35,9 @@ https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0 * [E-fun](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-fun) is for cool, but probably hard stuff. +# CI + +We use Travis for CI. Most of the things, including formatting, are checked by +`cargo test` so, if `cargo test` passes locally, that's a good sign that CI will +be green as well. We use bors-ng to enforce the [not rocket +science](https://graydon2.dreamwidth.org/1597.html) rule.