Document release process. (#225)

* Document release process.

* curl retry for linkcheck

* --retry-all-errors

.github/workflows/linkcheck.yml

@@ -23,7 +23,7 @@ jobs:
           set -eux
           if ! make linkcheck; then
             while read -r url; do
-              curl -sSfv -o /dev/null -w "%{http_code}" "$url" > docs/_build/html/status.txt
+              curl -sSfv --retry 3 --retry-max-time 45 --retry-all-errors -o /dev/null -w "%{http_code}" "$url" > docs/_build/html/status.txt
               grep '^200$' docs/_build/html/status.txt
             done < docs/_build/html/broken.txt
           fi

README.md

@@ -22,5 +22,13 @@ Google Analytics is enabled on my website via a [CloudFlare app](https://www.clo
 
 ## Releases
 
-Deployments to production are done by GitHub Actions when a new tag matching the format YYYY-MM-DD is manually pushed. All
-branch and tag pushes trigger a deployment to staging, whilst pull requests only trigger CI linting and testing.
+Releasing to stage is done automatically on every branch push.
+
+To release to production:
+
+1. https://github.com/Robpol86/robpol86.com/actions/workflows/release.yml
+1. Run workflow > Fill out the release title
+    1. This will also be the section title in the [CHANGELOG.md](CHANGELOG.md) entry
+1. Run workflow
+1. When it completes a new git tag, GitHub release, and CHANGELOG.md entry will be created
+1. The workflow will also deploy the HTML to production