Explore >> Select a destination
|
You are here 
|
andrewlester.net | ||
| | | | |
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.djpeacher.com
|
|
| | | | | If you want a quick (and free) way to deploy your Hugo site, using GitHub Action is a great option! | |
| | | | |
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? | |
| | | | |
briankung.dev
|
|
| | | I realized that one of my favorite Rust features doesn't have a blog post highlighting it [0], so I thought I'd talk a bit about documentation comments and doc tests in Rust. I'll give you a quick example. Let's say you have some code: There's a cargo command to generate documentation from that code: Which... | ||
