Switch to reusable CI flow
@jefftrull is already working on this.
Since Mar 18, 2026.
Assessment
This issue has not been assessed yet.
Description
We've had to periodically update our CI configs as old Github Actions test runners are deprecated. The latest is macos-13, currently causing our CI jobs to fail. Fortunately Boost's build experts have a solution: a reusable config that can be used straight out of the Boost-CI repo, as described here. We should switch to it to save on development effort and gain other benefits, like code coverage and static analysis.
- Dominant language
- C++
- Stars
- 29
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
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.
More from boostorg/wave
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Is it possible? Dumping preprocessor state at end of output so that preprocessing can be resumed? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·