ci: use the shared codestyle workflow - #30
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe codestyle workflow now runs on pull requests targeting any branch and delegates checks to a reusable workflow. The repository-specific codestyle script and its inline job configuration were removed. ChangesCodestyle CI
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkResolution Complete the pull request description with all required template sections. List the proposed changes, link any related issue or state that none applies, provide a source if available, document tests performed and the test environment, and add detailed steps to test the changes locally or in CI.
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Calls azerothcore/reusable-workflows instead of keeping a local copy of the workflow and
apps/ci/ci-codestyle.sh, the way core-build already does.Summary by CodeRabbit