Explicitly set repository name in the conventions plugins#6170
Conversation
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
|
No actionable comments were generated in the recent review. 🎉 WalkthroughAdded a new configuration property Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
|
|
🚀 Available in v6.32.4 |



Goal
The build conventions plugins, use the project name as a default for the repository name. That is used in things like spotless headers. I realized this has the downside that if you locally rename the project folder, spotless will try to change all headers. So instead I'm setting the name explicitly. I'll also make it mandatory in the plugin.
Implementation
Set the name
🎨 UI Changes
None
Testing
Try renaming the project folder and verify that
spotlessCheckpassesSummary by CodeRabbit