Add[#240]:CI add workflow for groovy checker #313
Closed
Conversation
This file contains 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
|
Hey @vivekvr1 thank you very much for the proposal! Did you have a chance to test this change? |
|
This PR is stale because it has been open for 90 days with no activity. |
|
This PR was closed because it has been inactive for 60 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes: #240
What is the purpose of the change
A new job named groovy-check was added.
The groovy-check job uses the actions/setup-java@v3 action to set up Java 11.
The groovy-check job runs the gradle groovy command to compile and check the Groovy code for errors.
A new step was added to the groovy-check job to fail the workflow if the Groovy checker finds any errors.
Improved code quality: The Groovy checker will help to ensure that the Groovy code is always error-free.
Reduced risk of regressions: The Groovy checker will help to identify and fix errors before they are deployed to production.
Increased confidence in the codebase: The Groovy checker will help to increase confidence in the codebase by ensuring that the Groovy code is always error-free.