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 document.
Useful labels on the issue tracker:
- E-mentor issues have links to the code in question and tests,
- E-easy, E-medium, E-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) is valid, but it's a good idea to write nice commit messages, test code thoroughly, maintain consistent style, etc.