Adopt shared Scala CI workflow - #26
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CI workflow now uses ChangesCI workflow unification
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: ⚪ Minimal · up to This change centralizes Scala CI configuration without any supplied evidence of a current correctness or production-impact risk; no actionable merge-blocking risk remains beyond normal checks and review. Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
Replaces the hand-written ci.yml with a call to the shared workflow, so tests, coverage, binary compatibility, formatting and scaladoc are configured centrally. Coverage stays off, as before. Binary compatibility is switched off explicitly because the repo has no sbt-version-policy; it was never enforced.
Checks now run as explicit sbt tasks rather than through the
checkalias, and checkout is unshallow so versionPolicyCheck has a previous version to compare against.Part of evolution-gaming/scala-github-actions#5
Summary by CodeRabbit