rust-lang / rust-lang/rust-analyzer
Improve our CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
There are a few things we can do better right now. For one no matter what change we retrigger the entire pipeline. This seems unnecessary, some files like the README for example don't need any checks at all.
Changing the typescript code shouldn't trigger rust builds and vice versa.
Changing something in the libs dir should ideally only test the changed lib, though given there is only one this isn't really too relevant atm.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no CI files, tests, or entry points. Start by locating the pipeline configuration and its path-based triggers, then determine how Rust, TypeScript, README, and other changes are currently classified. Done means unrelated changes no longer run unnecessary checks while relevant changes still trigger the required pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100