Explore >> Select a destination
|
You are here 
|
tomasvotruba.com | ||
| | | | |
chringel.dev
|
|
| | | | | This post shows an example workflow to automatically deploy the latest version of a Hugo website using GitHub Actions. | |
| | | | |
www.andrlik.org
|
|
| | | | | I've been using uv in my Github Actions workflows for a while now to speed up my runner environment creation, and I wanted to do the same for my publishing workflows. So, I created the following workflow for each of my PyPI packages. | |
| | | | |
davquar.it
|
|
| | | | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | |
| | | | |
www.morling.dev
|
|
| | | As a software engineer, I like to automate tedious tasks as much as possible. The deployment of this website is no exception: it is built using the Hugo static site generator and hosted on GitHub Pages; so wouldn't it be nice if the rendered website would automatically be published whenever an update is pushed to its source code repository? | ||
