Repository navigation
|
Hi Checkstyle maintainers and contributors! I've recently started contributing to Checkstyle and would appreciate some guidance on the recommended workflow for managing multiple contributions. I currently have three open pull requests:
I've also reported five reproducible functional bugs:
For these five issues, I've prepared local fixes with regression tests, and the full Maven verification has passed. However, I have not opened any PRs for them, since the issues are still awaiting the I understand that maintainer reviews take time, and I don't want to rush the process or create unnecessary notifications. I would appreciate guidance on a few points:
I'm interested in contributing to Checkstyle long-term and want to make sure I'm following the project's expectations and making useful contributions. Thanks for your time and guidance! |
Replies: 2 comments 4 replies
|
We do approval labels only to safe contributors times , as sometimes what users wants is not possible. activity in project now above maintainers abilities. |
|
Thank you @romani for clarifying, and for all the work maintaining Checkstyle! I understand that approving issues beforehand helps contributors avoid spending time on changes that might not be accepted. Just one clarification: the current contribution guidelines and PR template still mention that issues must have the I already have some fixes with regression tests and successful Maven verification prepared locally, so this would be really helpful. I'll keep the PRs focused, coordinate with other contributors, and avoid unnecessary review overhead. Thanks again! |
We do approval labels only to safe contributors times , as sometimes what users wants is not possible. activity in project now above maintainers abilities.
If issues are obvious defects , you can send PR to fix, we review issue as we get PR