Add bors to CI, or activate GH merge queue
Open
Nobody has claimed this yet.
C-technical-debt
P-low
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
This would have prevented master being red earlier this morning (#1049).
Steps to implement:
- Add the homu config (example)
- Add the permission on the team repo (example)
- Add a "bors build finished" CI job. Relevant code: https://github.com/rust-lang/crater/blob/dcc54566d5ec82cabca435c0145cbd06f32d3602/.github/workflows/bors.yml#L126-L150
The repo should be called docs-rs on the bors side.
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
Review the homu configuration example, the team-repository permission example, and the referenced bors CI workflow. Set up the docs.rs bors integration under the name docs-rs, grant the required team-repository permission, and add the "bors build finished" CI job; done means the chosen bors or GitHub merge-queue setup prevents merging with a red master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100