/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 simonwillison.net
Automatically opening issues when tracked file content changes
| | peterullrich.com
How to set up reoccurring jobs with GitHub Actions
2.0 parsecs away

Travel
| | How to automate a reoccurring job using GitHub Actions in order to fetch and upload latest data to a GitHub repository.
| | huey.xyz
Daisy-chaining GitHub actions | Huey
1.3 parsecs away

Travel
| | 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...
| | localheinz.com
Creating releases with GitHub Actions - Andreas Möller
2.0 parsecs away

Travel
| | Since GitHub introduced the automatic generation of release notes, creating releases with release notes has become easier than ever.
| | popey.com
Publishing Hugo site via GitHub Actions - Alan Pope's blog
9.9 parsecs away

Travel
| My blog at popey.com/blog is hosted on a Bitfolk VPS, built from the Hugo source code in a public GitHub repo. My workflow for publishing a post goes like this: Use whatever machine Im sat at Clone the repo Add a new page, edit until ready Push directly to the main branch Early on in my use of Hugo, I was manually using hugo and rsync over SSH directly on the VPS.