Explore >> Select a destination
|
You are here 
|
aayushsahu.com | ||
| | | | |
blog.railway.com
|
|
| | | | | Github Actions come with a pretty neat set of features to automate your workflows. In this post, we talk about using Github Actions to automate your deployments on Railway. | |
| | | | |
chringel.dev
|
|
| | | | | This post shows an example workflow to automatically deploy the latest version of a Hugo website using GitHub Actions. | |
| | | | |
huey.xyz
|
|
| | | | | Triggering a GitHub action from a git push from another GitHub action. This site is a static site with a deployment pipeline that comprises various daisy-chained GitHub actions. For example, there is a GitHub action that checks my BookWyrm orreadi.com profile periodically, and updates a JSON file in the GitHub repository for this site if there are changes to the books... | |
| | | | |
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? | ||
