rust-lang / rust-lang/cargo-bisect-rustc
Potentially use rustc-artifacts crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 206
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
https://docs.rs/rustc-artifacts/0.2.0/rustc_artifacts/fn.master_commits.html provides access to bors commit data that doesn't depend on the GitHub API. It provides less information than we might want today, but I would be willing to expand that (I'm the owner of the crate).
That crate currently uses a new triagebot API that lists bors commits made in the last 168 days, currently with just the sha, parent sha, and timestamp of the commit.
That would mean that we can run bisection entirely without the GITHUB_TOKEN or a local rust repository clone, and then use the GitHub API solely to lookup the commit details (if desired).
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 rustc-artifacts 0.2.0 master_commits documentation and its triagebot API description; no repository file or test is named in the issue. Determine whether its sha, parent sha, and timestamp data supports the existing bisection flow, and document what would be needed to avoid GITHUB_TOKEN and a local Rust clone while retaining optional commit details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100