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

Github action example with actions/cache usage #4372

Open
kravetsone opened this issue Nov 20, 2024 · 1 comment
Open

Github action example with actions/cache usage #4372

kravetsone opened this issue Nov 20, 2024 · 1 comment
Labels
contribution welcome The team would welcome a contribution from the community for this issue docs Improvements or additions to documentation stale

Comments

@kravetsone
Copy link

kravetsone commented Nov 20, 2024

continues of shikijs/shiki#840

We have .vitepress/cache directory which contains some files which vitepress uses as cache.

Does we should to include it in our workflow as step with actions/cache? For example:

- uses: actions/cache@v4
              with:
                  path: ./docs/.vitepress/cache
                  key: ${{ runner.os }}-vitepress-${{ hashFiles('**/bun.lockb') }}-${{ hashFiles('docs/**') }}
                  restore-keys: |
                      ${{ runner.os }}-vitepress

What are the best practices or pros and cons of using actions/cache on .vitepress/cache folder?

It would be great to include this in documentation

For now deploy#github-pages don't use it. Its just missed or it have some side-effects?

@brc-dd
Copy link
Member

brc-dd commented Nov 20, 2024

Should be fine I guess. We can add it.

@brc-dd brc-dd added docs Improvements or additions to documentation contribution welcome The team would welcome a contribution from the community for this issue labels Nov 20, 2024
@github-actions github-actions bot added the stale label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome The team would welcome a contribution from the community for this issue docs Improvements or additions to documentation stale
Projects
None yet
Development

No branches or pull requests

2 participants