[Automated] Standardize Ballerina.toml keywords#147
Conversation
keywords in Ballerina.toml
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated package keywords in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (75.30%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## master #147 +/- ##
=========================================
Coverage 75.30% 75.30%
Complexity 157 157
=========================================
Files 27 27
Lines 891 891
Branches 123 123
=========================================
Hits 671 671
Misses 191 191
Partials 29 29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Remove vendor keyword from codebase
This pull request standardizes package keywords in build-config/resources/Ballerina.toml to align with the project's taxonomy. The package keywords are now: ["jms", "Area/Messaging", "Type/Connector", "Type/Trigger"]. These changes are metadata-only and do not affect functional code, dependencies, or control flow.