Repository navigation
Make gradlew executable (mode 100755) - #6
Merged
Merged
Conversation
gradlew was committed with mode 100644, so on Linux and macOS the build fails with 'permission denied' before Gradle even starts. It was added from Windows, where git has core.filemode=false and cannot record the executable bit; a green build there says nothing about the mode. Same fix Tom applied to paymenthub-ee-vouchers in 9d9c849. Of all the paymenthub-ee-* repos this is the last one left with the wrong mode. No file content changes: same blob, only the index mode.
tdaly61
approved these changes
Aug 24, 2026
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
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.
gradlewis committed with mode100644, so on Linux and macOS the build fails withpermission deniedbefore Gradle starts. Same failure @tdaly61 hit onpaymenthub-ee-vouchersand fixed in 9d9c849; this is the lastpaymenthub-ee-*repo left with the wrong mode.Cause: the wrapper was added from Windows, where git has
core.filemode=falseand cannot record the executable bit — a green local build there says nothing about the mode. In this repo specifically the file came in through the multi-module bootstrap commit rather than from the original repo's git objects, which is why it landed100644here and100755in the other repos.Change:
git update-index --chmod=+x gradlew. No content change — same blobf5feea6, only the index mode. Diff is1 file changed, 0 insertions(+), 0 deletions(-).Note that nothing in CI would have caught this: the repo has no workflow that runs
./gradlewon Linux (onlycla-check.yml, and CircleCI isn't wired up), so the first Linux execution is always a human's. Happy to add the GitHub Actionstest.ymlhere as a follow-up if you want that closed properly.