brozek/website
1
0
Fork 0
mirror of https://github.com/Brandon-Rozek/website.git synced 2025-10-09 14:31:13 +00:00
Code Issues Projects Releases Packages Activity

Fixed links

Browse source
This commit is contained in:
Brandon Rozek 2023-09-26 17:43:41 -04:00
parent 18ca6cae06
commit 1bb95f36d7
No known key found for this signature in database
GPG key ID: 26E457DA82C9F480
27 changed files with 100 additions and 100 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/blog/deploying-hugo-website-through-gh-actions.md
View file

@ -13,7 +13,7 @@ For the longest time I've held out on deploying my website through GitHub action
> If I have to execute `git push`, I might as well run a `./sync` script afterwards.
What convinced me otherwise is automated commits. I currently have GitHub actions that sync my [Mastodon toots](/toots) and [iNaturalist observations](/observations). As part of the sync process, a git commit is made. This commit should then trigger a site rebuild.
What convinced me otherwise is automated commits. I currently have GitHub actions that sync my [Mastodon toots](/toots/) and [iNaturalist observations](/observations/). As part of the sync process, a git commit is made. This commit should then trigger a site rebuild.
How do we create a GitHub action that builds a Hugo website and deploys it via `rsync`? The rest of this post will go over the components of the GitHub action that triggers when I update my website.