oxidecomputer / oxidecomputer/omicron
Switch to using a merge queue
Open
Nobody has claimed this yet.
development
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Breakages like https://github.com/oxidecomputer/omicron/pull/4580 are likely going to get more common over time as development on omicron continues.
We should consider switching to a merge queue where at least some portion of CI checks are performed linearly.
Tasks:
- Investigate options and write an RFD
- If we decide to go ahead, determine the subset of checks that will be done via a merge queue.
- Implement
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 reviewing the breakage described in pull request 4580 and investigate merge-queue options for the project's CI. Write an RFD, identify which checks should run through the queue, and implement the chosen approach if approved; done means the decision and selected checks are documented and the implementation is working.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100