-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Gradle check should be required before merging changes #12735
Comments
My thoughts are that I do not think changes should be mergeable unless they pass the gradle check - save a justification that the admin team agrees with and then performs the override. |
Thanks a lot @bbarani ! |
@peternied Please note that the referred PR has not introduced any test defects. The failing tests are due to some other changes which have been fixed by the respective owners |
Describe the bug
Pull requests have been merged without a passing gradle check introducing defects into main. [1] The gradle check is the minimal bar that all changes should pass before they are merged into main to ensure consistent code quality.
Expected behavior
Pull requests should only be allowed to merge without a passing gradle check by the Admin team for the project.
Additional Details
Additional context
The text was updated successfully, but these errors were encountered: