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

docs: fix source files hash calculation #54509

Merged
merged 2 commits into from Aug 25, 2023
Merged

docs: fix source files hash calculation #54509

merged 2 commits into from Aug 25, 2023

Conversation

ClementDreptin
Copy link
Contributor

Hello!

I recently tried to cache the .next/cache directory in a GitHub action following what was said in the documentation and realized that hashing the source files didn't work properly.

This problem also occured in next-cache and was fixed by this PR.

This PR simply changes the example from the documentation to apply the same fix (stop using brackets in the patterns passed to hashFiles).

Hope it helps!

Improving Documentation

Copy link

@orca-security-us orca-security-us bot left a comment

Choose a reason for hiding this comment

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

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca

Copy link
Member

@ijjk ijjk left a comment

Choose a reason for hiding this comment

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

Copy link
Member

@balazsorban44 balazsorban44 left a comment

Choose a reason for hiding this comment

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

JJ, it looks to be the recommendation for hashFiles here: https://docs.github.com/en/actions/learn-github-actions/expressions#example-with-multiple-patterns

So the PR looks good to me. Thanks!

@ijjk
Copy link
Member

ijjk commented Aug 25, 2023

Allow CI Workflow Run

  • approve CI run for commit: 72566bd

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@styfle styfle added the CI approved Approve running CI for fork label Aug 25, 2023
@kodiakhq kodiakhq bot merged commit 41be932 into vercel:canary Aug 25, 2023
47 checks passed
@github-actions github-actions bot added the locked label Sep 9, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI approved Approve running CI for fork locked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants