matrix-org / matrix-org/matrix-rust-sdk
Merge CI jobs `🕸️ [m]-base`, `🕸️ [m]-common`?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
These two CI jobs should both never affect each other, and take longer to compile than run. Should we merge them, either in `xtask::ci` or at the GH actions level?
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
Start by inspecting the 🕸️ [m]-base and 🕸️ [m]-common jobs, then read the related logic in xtask::ci and the GitHub Actions configuration. Compare whether merging at either layer preserves their independence and compile/run behavior. Done means the two jobs are combined without one affecting the other and CI still completes correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100