Materialize gradle-wrapper.jar from LFS before Gradle run#6
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the reusable “Dismiss dev-only Dependabot alerts” workflow to handle caller repositories that store gradle/wrapper/gradle-wrapper.jar in Git LFS, ensuring ./gradlew can run during the Gradle-based analysis phase.
Changes:
- Keep
actions/checkoutLFS disabled to avoid downloading all LFS objects by default. - Add a targeted
git lfs pull --include="gradle/wrapper/gradle-wrapper.jar"step immediately after checkout to materialize only the Gradle wrapper JAR when it’s LFS-tracked.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Some caller repos store gradle-wrapper.jar in Git LFS (e.g. an
*.jar filter=lfsrule). The checkout above leaves it as a pointer file, which the JVM rejects as "Invalid or corrupt jarfile". Pull only that one object so./gradlewcan launch. No-op on repos without LFS.