ci: Run Gradle wrapper validation only on Gradle files changes #1828
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SrinivasanTarget
approved these changes
Jan 5, 2023
saikrishna321
approved these changes
Jan 5, 2023
mykola-mokhnach
approved these changes
Jan 5, 2023
valfirst
deleted the
ci-run-gradlew-wrapper-validation-only-on-gradle-files-changes
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change list
It's not needed to validate Gradle wrapper for each and every change, it should be enough to run it only if particualr Gradle files are changed.
Types of changes
What types of changes are you proposing/introducing to Java client?