setup-node
checkout
Our great sponsors
setup-node | checkout | |
---|---|---|
24 | 62 | |
3,579 | 5,203 | |
3.9% | 3.0% | |
7.5 | 7.0 | |
11 days ago | about 5 hours 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.
setup-node
-
CI/CI deploy a static website to AWS S3 bucket through Github Actions
Setup environment with Nodejs and install dependencies with npm install, with Github Actions setup Node
-
VSCodium โ Libre Open Source Software Binaries of VS Code
No, PR review isn't the only thing that prevents these from being updated. In the yml it's set to a release branch. So it isn't especially fallible.
- Disable Annotations in Github Actions
-
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
-
Cheap Gatsby/Netlify-style Hosting?
steps: # Check out the current repository code - uses: actions/checkout@v3 # 3. https://github.com/actions/setup-node#usage - name: Setup node and build Gatsby uses: actions/setup-node@v1 with: node-version: '16.x' cache: 'npm' - run: npm install # This triggers `gatsby build` script in "package.json" - run: npm run build # 4. Deploy the gatsby build to Netlify - name: Deploy to netlify uses: netlify/actions/cli@master env: NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }} NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }} with: # 5. "gatsby build" creates "public" folder, which is what we are deploying args: deploy --dir=public --prod secrets: '["NETLIFY_AUTH_TOKEN", "NETLIFY_SITE_ID"]'
-
5 Ways to make development with GitHub Actions more efficient
If you see repeated build or preparation steps that do not change when your codebase changes, look into caching the results. Here is a straightforward guide to caching, but also be aware caching is built into a lot of marketplace actions anyway, e.g. actions/setup-node can cache npm dependencies.
-
Top 10 GitHub Actions You Should Use to set up your CI/CD Pipeline
The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.
-
The strongest principle of the blog's growth lies in the human choice to deploy it
diff --git a/.github/workflows/gh-pages.yaml b/.github/workflows/gh-pages.yaml index 401fd33..3ddf6dd 100644 --- a/.github/workflows/gh-pages.yaml +++ b/.github/workflows/gh-pages.yaml @@ -11,42 +11,48 @@ on: jobs: deploy: - runs-on: ubuntu-20.04 + runs-on: ubuntu-22.04 + # Ensure that only a single job or workflow + # https://docs.github.com/en/actions/using-jobs/using-concurrency concurrency: + # workflow - The name of the workflow. + # ref - The branch or tag ref that triggered the workflow run. group: ${{ github.workflow }}-${{ github.ref }} steps: - uses: actions/checkout@v3 with: - submodules: true # Fetch Hugo themes (true OR recursive) fetch-depth: 0 # Fetch all history for .GitInfo and .Lastmod + # https://github.com/peaceiris/actions-hugo - name: Setup Hugo uses: peaceiris/actions-hugo@v2 with: - hugo-version: '0.91.2' - # extended: true + hugo-version: '0.101.0' + # https://github.com/actions/setup-node - name: Setup Node uses: actions/setup-node@v3 with: - node-version: '14' - - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: ~/.npm - key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }} - restore-keys: | - ${{ runner.os }}-node- - - - run: npm ci + node-version: '18.7.0' + cache: npm + # The action defaults to search for the dependency file (package-lock.json, + # npm-shrinkwrap.json or yarn.lock) in the repository root, and uses its + # hash as a part of the cache key. + # https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#caching-packages-data + cache-dependency-path: ./blog/package-lock.json + + - name: Install npm dependencies + working-directory: ./blog/ + run: npm ci - name: Build - run: hugo --minify + working-directory: ./blog/ + run: npm run build + # https://github.com/peaceiris/actions-gh-pages - name: Deploy uses: peaceiris/actions-gh-pages@v3 if: ${{ github.ref == 'refs/heads/main' }} with: github_token: ${{ secrets.GITHUB_TOKEN }} - publish_dir: ./public + publish_dir: ./blog/src/public
-
How Fastly manages its software with GitHub Actions
Well, letโs consider the scenario we had with the DevHub. We were using the third-party action setup-node to install and configure the Node.js programming language. This action lets you specify the node version to install but it canโt be a dynamically acquired value. You either have to hardcode it or interpolate the value.
-
GitHub Actions Is Down
This is hitting workflows that use caching [1][2].
- [1] https://github.com/actions/setup-node/issues/516
- [2] https://github.com/actions/cache/issues/820
As of now (11:28 UTC) the status page has been updated.
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โฆ
- 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?
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
ssh-action - GitHub Actions for executing remote ssh commands.
setup-buildx-action - GitHub Action to set up Docker Buildx
cache - Cache dependencies and build outputs in GitHub Actions
upload-artifact
actions-gh-pages - GitHub Actions for GitHub Pages ๐ Deploy static files and publish your site easily. Static-Site-Generators-friendly.
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
act - Run your GitHub Actions locally ๐
add-and-commit - :octocat: Automatically commit changes made in your workflow run directly to your repo
nextjs-monorepo-example - Collection of monorepo tips & tricks
jacoco-badge-generator - Coverage badges, and pull request coverage checks, from JaCoCo reports in GitHub Actions