-
Notifications
You must be signed in to change notification settings - Fork 550
Open
Labels
A-contributor-onboardingArea: contributor on-boarding advice (e.g. for new contributors)Area: contributor on-boarding advice (e.g. for new contributors)C-enhancementCategory: enhancementCategory: enhancementE-easyDifficulty: might be a good place for a beginnerDifficulty: might be a good place for a beginnerT-compilerRelevant to compiler teamRelevant to compiler team
Description
Currently this is documented as
If your machine is not very powerful, a common strategy is to only use ./x.py check on your local machine and let the CI build test your changes when you push to a PR branch.
But it's hidden all the way down in https://rustc-dev-guide.rust-lang.org/building/prerequisites.html#hardware, which is a long way away from https://rustc-dev-guide.rust-lang.org/contributing.html#pull-requests (which is itself not easy to find).
We should
- Add a note near the 'pull request' section that Rust has plenty of CI capacity for PRs and it's fine to use it
- Make the pull request section easier to find
- Link to it from more places
For context, this is meant to be a replacement for rust-lang/rust#76272.
Metadata
Metadata
Assignees
Labels
A-contributor-onboardingArea: contributor on-boarding advice (e.g. for new contributors)Area: contributor on-boarding advice (e.g. for new contributors)C-enhancementCategory: enhancementCategory: enhancementE-easyDifficulty: might be a good place for a beginnerDifficulty: might be a good place for a beginnerT-compilerRelevant to compiler teamRelevant to compiler team