setup-node
actions-hugo
Our great sponsors
setup-node | actions-hugo | |
---|---|---|
24 | 10 | |
3,579 | 1,341 | |
3.9% | - | |
7.5 | 4.5 | |
11 days ago | 2 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.
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.
actions-hugo
-
Deploy Hugo to NixOS on Push to Gitea
You can build your Hugo site in your Github Actions, e.g. like in https://github.com/peaceiris/actions-hugo, then push the static pages to your server
-
The strongest principle of the blog's growth lies in the human choice to deploy it
Documentation provides an example workflow file that uses GitHub Actions for Hugo action in the "Build Hugo With GitHub Action" section. It is ok to use it, but I will use combination of 2 examples (1, 2) from GitHub Actions for Hugo's README because it has one for projects using PostCSS.
-
GitHub Actions Reporting My ❤️ Music
If the data fetch from previous step succeeds, the workflow continues by building the static website with Hugo. Hugo is setup using action peaceiris/actions-hugo. When the files are ready, the result is published to GitHub pages, using another GitHub action, peaceiris/actions-gh-pages.
-
How to Create a Workflow for HUGO Website hosted on GitHub Pages
Luckily, there is a workflow for it. By implementing peaceiris/actions-hugo@v2 on my GitHub workflow, I was able to achieve what I wanted to do. Simple as that.
-
What is your stack for your blog?
Less is more IMO. A Github Action using Hugo to deploy to GH pages.
-
Deploy Hugo website using Github pages
For more information about the actions used and their options, please see Hugo and Github pages on Github.
-
Help Wanted to Setup Non-Commertial Buddhist Website: dhammo.org (dhammo is the plural for of dhamma)
I am looking for someone who can help me, pro bono, to: - set up this site using GitHub Pages - set up Hugo SSG (https://gohugo.io) using Jane (https://github.com/xianmin/hugo-theme-jane) as the theme - set up automatic building using GitHub actions perhaps using https://github.com/peaceiris/actions-hugo - set up Giscus (https://giscus.app) for comments (may need to fork theme, if so try to up a steam a PR also so a separate fork does not need to be maintained.) - set up banner art and profile picture (may need to fork theme, if so try to up a steam a PR also so a separate fork does not need to be maintained.) - set up SEO, RSS, favicon, Analytics, etc.
-
Hugo on Azure with Static Web Apps
View on GitHub
-
How to use Firebase to host a Hugo site
I set up Hugo with peaceiris/actions-hugo. The build step afterwards runs the command
What are some alternatives?
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
Jekyll - :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
setup-buildx-action - GitHub Action to set up Docker Buildx
actions-mdbook - GitHub Actions for mdBook (rust-lang/mdBook) ⚡️ Setup mdBook quickly and build your site fast. Linux (Ubuntu), macOS, and Windows are supported.
upload-artifact
Hugo - The world’s fastest framework for building websites.
checkout - Action for checking out a repo
actions-gh-pages - GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.
wordpress-markdown-git - :loop: WordPress plugin to add file content (Markdown, Jupyter notebooks) from a Git based VCS to a WordPress post; replaces https://github.com/gis-ops/md-github-wordpress
act - Run your GitHub Actions locally 🚀
Oryx - Build your repo automatically.