Google Git
Sign in
fuchsia / third_party / github.com / rust-lang / rust-analyzer / c99bb3c782a9c110edc906bb4a01f4bea173d48e
commitc99bb3c782a9c110edc906bb4a01f4bea173d48e[log] [tgz]
authorbors <bors@rust-lang.org>Sat Jul 22 16:53:21 2023 +0000
committerbors <bors@rust-lang.org>Sat Jul 22 16:53:21 2023 +0000
tree71c4a92a073c38a5388c605efcffa11562a3dd69
parentb17be2720a2752f210796809355461d71770401e [diff]
parent5cca093fa856aafb0d6608d0fedbc40b731d855e [diff]
Auto merge of #15281 - tetsuharuohzeki:split-ci-steps, r=lnicola

editor/code: Break down CI steps to know what is failing easily

This do the thing I mentioned in https://github.com/rust-lang/rust-analyzer/pull/15265#issuecomment-1634424385

This aims to improve CI status check more readable.

I tried to use [`jobs.<job_id>.if`](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif) to make the configuration
more shortly once.

But it could not fire the `end-success` or `end-failure` status if some jobs in the workflow were skipped. This causes an integration problem with bors.

By their reasons, this patch still uses `jobs.<job_id>.steps[*].if`.

---

To do this change, we reorganize npm-script.

| previous           | after                                  |
|--------------------|----------------------------------------|
| `npm run lint`     | `npm run lint && npm run format:check` |
| `npm run fix`      | `npm run lint:fix && npm run format`   |

The previous `npm run fix` sometimes does not complete fix automatically because ESLint's autofix doees not follow prettier's formatting. So we need to run `npm run lint:fix && npm run format` by this order.
tree: 71c4a92a073c38a5388c605efcffa11562a3dd69
  1. .cargo/
  2. .github/
  3. .vscode/
  4. assets/
  5. bench_data/
  6. crates/
  7. docs/
  8. editors/
  9. lib/
  10. xtask/
  11. .editorconfig
  12. .git-blame-ignore-revs
  13. .gitattributes
  14. .gitignore
  15. Cargo.lock
  16. Cargo.toml
  17. LICENSE-APACHE
  18. LICENSE-MIT
  19. PRIVACY.md
  20. README.md
  21. rustfmt.toml
  22. triagebot.toml
README.md

rust-analyzer is a modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.

Quick Start

https://rust-analyzer.github.io/manual.html#installation

Documentation

If you want to contribute to rust-analyzer or are just curious about how things work under the hood, check the ./docs/dev folder.

If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Security and Privacy

See the corresponding sections of the manual.

Communication

For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:

https://users.rust-lang.org/c/ide/14

For questions about development and implementation, join rust-analyzer working group on Zulip:

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer

Quick Links

License

rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.