CI should be pinned to a particular rustc version
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 694
- Forks
- 336
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
It is currently very common that one makes a stdarch PR and CI fails despite the PR being correct -- in other words, stdarch master regularly fails its own CI. This is caused by CI automatically testing against the latest nightly version of rustc, while this repo uses tons of very unstable features. This is not a great contributor experience.
It would be better if CI tested some pinned rustc nightly / commit, so that one can be sure that red CI in a PR is actually caused by the changes on that PR.
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
Locate the repository's CI configuration and identify the job that selects the latest nightly rustc. Read how that toolchain is chosen, then pin it to a nightly version or commit and verify that pull-request CI uses the pinned toolchain rather than the latest nightly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100