rust-lang / rust-lang/rustc_codegen_gcc
Reorganize the GitHub Actions jobs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 105
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 14
Description
Maybe we could use job summaries to provide a summary of the number of passing tests in the failing CI jobs as well as showing the failing jobs that should pass:
- https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/
- https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary
Maybe we could group failing jobs together. See this:
Contributor guide
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 repository's GitHub Actions workflow definitions and the linked job-summary and visualization documentation. Determine how to group failing jobs and report passing-test counts, then verify that the workflow summary presents the intended grouping and statuses.
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
- Needs clarification
- Newbie friendliness
- 35/100