ci: use shared pixi-cmake-build reusable workflow#9
Conversation
Replaces the inline build/test workflow with a thin caller of ShipSoft/.github's pixi-cmake-build.yml. Identical behaviour (pixi run test on ubuntu-latest with cache), shared with FairShip, geometry, and ship-conda-recipes.
|
Warning Review limit reached
More reviews will be available in 14 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
Swaps `.github/workflows/build-test.yml` for a thin caller of
`ShipSoft/.github/pixi-cmake-build.yml`.
Behaviour is identical (`pixi run --locked test` on ubuntu-latest
with pixi cache); the workflow body lives once centrally and is
shared with FairShip, Geometry, and ship-conda-recipes.
Test plan