Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the recommended gradle/actions/setup-gradle@v3 #478

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

wmdietl
Copy link
Collaborator

@wmdietl wmdietl commented Feb 7, 2024

#476 suggests doing this update instead of merging #476.

@wmdietl wmdietl requested a review from netdpb February 7, 2024 02:06
@@ -76,15 +76,15 @@ jobs:
- name: Run Conformance Tests
if: github.base_ref == 'main' # only PRs onto main
continue-on-error: true
uses: gradle/gradle-build-action@v2
uses: gradle/actions/setup-gradle@v3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the recommended pattern is to have a single, separate step to set up Gradle, and then to just run Gradle as a normal shell invocation.

See the publish-snapshot job above.

@cpovirk
Copy link
Collaborator

cpovirk commented May 23, 2024

#476 suggests doing this update instead of merging #476.

Oops, sorry: I was merging old PRs (since those contain versions of files without licenses, which upsets our licensing tooling), and I merged that one before noticing this. Obviously we could still do this, but you'll now have a merge conflict :\

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants