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

Describe cache key format in readme #215

merged 1 commit into from Dec 29, 2021

Describe cache key format in readme #215

merged 1 commit into from Dec 29, 2021


Copy link

Several users, including myself, wondered what cache key format is being used under the hood (see e.g. here or here). This PR adds a corresponding description – based on computeCacheKey – to the

Related issue:

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

copybara-service bot pushed a commit to google/google-java-format that referenced this pull request Sep 9, 2021
As of August 30, ["`setup-java` supports caching for both Gradle and Maven projects"]( This helps to reduce the amount of boilerplate code in the workflow file.

More details can be found in the [corresponding docs]( (And if you wonder what's the used cache key format: actions/setup-java#215)

Fixes #660

COPYBARA_INTEGRATE_REVIEW=#660 from beatngu13:patch-1 47e262b
PiperOrigin-RevId: 395674252
Copy link
Contributor Author

@dmitry-shibanov thank you for reviewing and approving. That was 20 days ago, is there anything else I can do get this merged?

Copy link

Hello @beatngu13! Thank you for the contribution!

@MaksimZhukov MaksimZhukov merged commit 04d5353 into actions:main Dec 29, 2021
1 check passed
@beatngu13 beatngu13 deleted the update-readme-cache-key branch Dec 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants