Merged
Conversation
Signed-off-by: solonovamax <solonovamax@12oclockpoint.com>
|
Matyrobbrt
approved these changes
Feb 1, 2025
|
🚀 This PR has been released as snowblower version |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Currently, the
gradlewscript is not marked as executable when cloned on linux, due to the file permissions being set to644rather than the expected755.This PR marks it as executable, so when cloned on a linux system, it will not require being manually
chmod'd by the user.It is especially convenient for people like me who use tools like gradle-autowrap, which allows me to do
gradle [task name]rather than./gradlew [task name]and it will automatically decide whether to use the project gradle version (ifgradlewexists & is executable) or the system gradle version.