rust-lang / rust-lang/rustc-dev-guide
Document how to find the nightly version that a beta/stable was branched from
Open
Nobody has claimed this yet.
A-git
C-enhancement
E-hard
T-release
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
this is what I have so far, might be something more reliable. doesn't work before ~1.65.
; rustc_version_bump=$(git log --format=%H -n1 -G CURRENT_RUSTC_VERSION origin/beta -- compiler/rustc_feature/src/accepted.rs)
; git log --format=%H -n1 --author=bors $rustc_version_bump
Contributor guide
No contributing guide indexed for this repository
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
Start with the proposed git commands and compiler/rustc_feature/src/accepted.rs, checking how the beta branch and CURRENT_RUSTC_VERSION history relate. Investigate a reliable method for versions before and after approximately 1.65, then document the steps and limitations in the appropriate guide section. Done means a newcomer can identify the nightly version from which a beta or stable release was branched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100