rust-embedded / rust-embedded/cortex-m
CI workflows should have a single job as the pass/fail gate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 202
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
Github requires us to type job names into the UI to set the pass/fail criteria for a PR build. This makes changing job names very difficult to synchronise (you have to merge a failing PR and then fix the UI after the fact).
rust-embedded/aarch32-cpu has a single job to indicate "pass/fail", and all the other jobs feed into it. For reasons, the job is "skipped on pass, failed on fail" but the UI is fine with that.
We should do that with this repo.
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 by reading the repository's CI workflow definitions and identify how jobs currently determine the PR status. Compare that structure with the single-gate pattern described for rust-embedded/aarch32-cpu, then verify that the configured PR check has one stable pass/fail job and that the other jobs feed into it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100