Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

ci: Use gatsby-cache action to cache gatsby build outputs#3033

Merged
ovflowd merged 3 commits into
nodejs:mainfrom
jongwooo:ci/use-gatsby-cache-action-to-cache-gatsby-build-outputs
Nov 25, 2022
Merged

ci: Use gatsby-cache action to cache gatsby build outputs#3033
ovflowd merged 3 commits into
nodejs:mainfrom
jongwooo:ci/use-gatsby-cache-action-to-cache-gatsby-build-outputs

Conversation

@jongwooo

Copy link
Copy Markdown
Contributor

Signed-off-by: jongwooo jongwooo.han@gmail.com

Description

I created an action to cache Gatsby's build outputs. This action is easy to set up.

AS-IS

- name: Gatsby Cache Folder
  uses: actions/cache@v3
  with:
    key: cache-folder-ubuntu-latest
    path: .cache

- name: Gatsby Public Folder
  uses: actions/cache@v3
  with:
    key: public-folder-ubuntu-latest
    path: public

TO-BE

- uses: jongwooo/gatsby-cache@v1.1.0
  with:
    key: build-gatsby-ubuntu-latest

References

Related Issues

N/A

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
    • This is important as most of the cases your code changes might not be correctly linted
  • I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
  • I have checked that the build works locally and that npm run build work fine.
  • I've covered new added functionality with unit tests if necessary.

@ovflowd ovflowd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good enough to me! Nice job on making your own GitHub Action :)

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

Base: 66.02% // Head: 68.17% // Increases project coverage by +2.15% 🎉

Coverage data is based on head (fb6efda) compared to base (fd57b87).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3033      +/-   ##
==========================================
+ Coverage   66.02%   68.17%   +2.15%     
==========================================
  Files         118      145      +27     
  Lines        1351     1656     +305     
  Branches      342      388      +46     
==========================================
+ Hits          892     1129     +237     
- Misses        422      484      +62     
- Partials       37       43       +6     
Impacted Files Coverage Δ
src/templates/blog.tsx 0.00% <0.00%> (-100.00%) ⬇️
util-node/getNodeReleasesData.js 91.30% <0.00%> (-6.32%) ⬇️
src/__fixtures__/page.tsx 94.11% <0.00%> (-5.89%) ⬇️
src/pages/index.tsx 100.00% <0.00%> (ø)
src/templates/api.tsx 0.00% <0.00%> (ø)
src/templates/learn.tsx 100.00% <0.00%> (ø)
util-node/createSlug.js 100.00% <0.00%> (ø)
util-node/getNvmData.js 100.00% <0.00%> (ø)
src/hooks/useOnScreen.tsx 100.00% <0.00%> (ø)
src/pages/about/index.tsx 100.00% <0.00%> (ø)
... and 184 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@ovflowd ovflowd merged commit c928244 into nodejs:main Nov 25, 2022
@jongwooo jongwooo deleted the ci/use-gatsby-cache-action-to-cache-gatsby-build-outputs branch November 26, 2022 01:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants