feat(ci): cache github workflow actions

[G3root]

No description provided.

[vercel]

@G3root is attempting to deploy a commit to the Documenso Team Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are limited to the following labels: coderabbit. Please add one of these labels to enable auto reviews.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit's AI:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[adithyaakrishna]

@G3root This would be a good improvement to the CI, I was planning to cache the build artifact yesterday and I guess it's been implemented already

[G3root]

from https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#force-deleting-cache-entries

[G3root]

from https://docs.docker.com/build/ci/github-actions/cache/#local-cache

[Mythie]

I thought that the npm cache was already satisfactory? Was I wrong in that assumption 🤔

Work looks really good either way, although I wonder what the cost of this will look like 👀

[adithyaakrishna]

If I am not wrong, I guess we would be using a built version of Documenso instead of rebuilding it again and again unless code stuff has changed. Along with this, I guess we would also be caching node_modules in a better way. Overall this may give us a slight advantage in terms of the CI timings

CC @G3root

[G3root]

If I am not wrong, I guess we would be using a built version of Documenso instead of rebuilding it again and again unless code stuff has changed. Along with this, I guess we would also be caching node_modules in a better way. Overall this may give us a slight advantage in terms of the CI timings

CC @G3root

yeah, we can go with that approach, but I believe it carries some risk because Changes in environment variables could affect the build output. Or, we can try experimenting with TurboRepo to manage the cache. https://turbo.build/repo/docs/ci/github-actions#caching-with-github-actionscache

[Mythie]

Sorry for the delay, approving but delaying merging for the moment since I'd like to limit some blast radius.

/remindme 1 week

[Mythie]

/tip 150

The work is much appreciated by the way 😄

[algora-pbc]

🎉🎈 @G3root has been awarded $150! 🎈🎊

• Share on socials
• Give feedback