Publishing My Site

Nothing is Ever Simple

Before I could even start to figure out publishing my site, I had to figure out why the git.gay was not synced up. Long story short I made 2 projects and had been developing on the one that was not connected to my git account. I fixed that by copying the files over to the teahouse project and committed those changes. Unfortunately, I forgot to do the git fetch before my commit so I had to fix the remote branch by doing a merge of the two branches.

Now to Actually Publish

Once I got that fixed, I was directed to look at the CI/CD (“actions”) to run a build of the site. I found them under the actions tab in git.gay and re-ran the tests. Tests 2-4 succeeded but task 1 failed. Jamie said that it will always fail so not to worry.

With that done I turned my attention to writing out the Build Job for my site in the publish.yaml file. Jamie provided an example site for me to use in figuring out mine. It took a bit but I was able to understand the required Github actions to build my site and how to learn more about them.

Finally I had to fill out the Deployment Job. This one was easier because I was more familiar with the Github Actions and their docs. The main issue I ran into with both the final step of the Build and the first step of the Deploy is that “upload-artifact@v4+ and download-artifact@v4+ are not currently supported on GHES”. However, the supported versions for each are different. For upload-artifact the supported version is v3.2.2 but for download-artifact it is just v3.

Once I got the versions ironed out, all the jobs completed successfully and I was able to publish my site.