cache
checkout
Our great sponsors
cache | checkout | |
---|---|---|
40 | 62 | |
4,250 | 5,203 | |
2.4% | 3.6% | |
7.4 | 7.0 | |
9 days ago | 6 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cache
-
GitHub Actions could be so much better
> with no persistent storage
There's https://github.com/actions/cache though?
-
Optimizing GitHub Actions Performance: Enhance Workflows with Caching
Use Cache Actions: GitHub Actions provides cache actions that simplify caching implementation. The @actions/cache JavaScript library is a popular choice for managing caching in workflows. It offers flexible options for storing and retrieving cache artifacts based on keys, scopes, and paths.
-
Speeding up GitHub Actions with npm cache
GitHub maintain a set of repos called actions. One of which is called cache.
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
By utilizing the actions/cache action action, we implemented a strategy to store and retrieve dependencies, preventing redundant installations.
-
Use GitHub Actions to Make Your GitHub Profile Dynamic
I do think it's good practice to enable caching, such that your script doesn't hit RubyGems / pip / npm / etc every time it runs.
That way at least the automation activity stays entirely within the GitHub / Azure network.
It looks like you can do that for Ruby by adding this:
https://github.com/actions/cache/blob/master/examples.md#rub...
- uses: ruby/setup-ruby@v1
-
A guide to using act with GitHub Actions
β getting-started-with-act git:(master) act -j build WARN β You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. β [Node.js CI/build] π Start image=node:16-buster-slim [Node.js CI/build] π³ docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] π³ docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] π³ docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] β git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] β git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] β git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] β Run Main actions/checkout@v3 [Node.js CI/build] π³ docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] β Success - Main actions/checkout@v3 [Node.js CI/build] β Run Main Use Node.js 16.x [Node.js CI/build] π³ docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] π³ docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] π¬ ::debug::isExplicit: [Node.js CI/build] π¬ ::debug::explicit? false
- duplicated cache by cache action
-
runner image with MS office installed - do-able? is there a better way?
You could try to find some point in the process where you can set up Actions caches with actions/cache, otherwise Container customization for Self-Hosted Runners is currently in Beta.
-
[Question] Decrease Docker image's build time
I would configure Github Actions cache so Docker doesn't have to compile all layers from scratch every time
-
The strongest principle of the blog's growth lies in the human choice to deploy it
In the copied example, npm caching is done via actions/cache@v2 action. But we can simplify our workflow by dropping this step and using built-in functionality for caching
checkout
-
Learning GitHub Actions in a Simple Way
checkout
-
Secure GitHub Actions by pull_request_target
To checkout the merged commit with actions/checkout on pull_request_target event, you need to get the pull request by GitHub API and set the merge commit hash to actions/checkout input ref.
-
Tell HN: PR GitHub Actions don't run over your commit by default
If you re-run GHA after master changes, CI is testing over different code.
You can [disable](https://github.com/actions/checkout#checkout-pull-request-head-commit-instead-of-merge-commit) on the checkout action:
```
-
GitHub Is Down
There was an outage yesterday too when the GitHub action βcheckout@v3β broke when they released βcheckout@v4β
Yes, they broke the ability for GitHub CI to checkout reposβ¦
https://github.com/actions/checkout/issues/1448
- Can't use 'tar -xzf' extract archive file
-
Building project docs for GitHub Pages
The first two steps are setting up the job's environment. The checkout action will checkout out the repository at the triggering ref. The setup-python action will setup the desired Python runtime. My package supports Python 3.9+ so I'm targeting the minimum version for my build environments.
-
Automating GitHub Profile Updates with GitHub Actions
These first few steps demonstrate how you can run commands like npm install or import other workflows such as how it uses the actions/checkout to copy the contents of the repository into a working directory on the runner host. Read Reusable workflows for more about the syntax for referencing them.
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions π³π
Check out the repo: We will use the actions/checkout action to checkout the repository.
-
[Actions] How do I take my dev branch, build it, and then create a pull request to main with the latest build artifacts?
Take a look at the checkout action usage here https://github.com/actions/checkout
-
Using Github Actions to publish your Flutter APP to Firebase App Distribution
Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.
What are some alternatives?
upload-artifact
ssh-action - GitHub Actions for executing remote ssh commands.
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
setup-node - Set up your GitHub Actions workflow with a specific version of node.js
act - Run your GitHub Actions locally π
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
setup-buildx-action - GitHub Action to set up Docker Buildx
add-and-commit - :octocat: Automatically commit changes made in your workflow run directly to your repo
setup-qemu-action - GitHub Action to install QEMU static binaries
jacoco-badge-generator - Coverage badges, and pull request coverage checks, from JaCoCo reports in GitHub Actions