Bump @actions/core

Security update - Bump @actions/core from 1.5.0 to 1.9.1

v2.1 - Nothing to commit no longer throws a failure

Fix: Build process no longer throws an error when there are no changes to commit. Safe exit instead. This was mainly done to prevent the whole workflow from failing.

v2 - Refactor with new release pattern

v2 is back! I don't know why it disappeared in the first place, but I took the strange opportunity to rewrite a large chunk of it and make it work better than before.

Please note that I renamed many variables in v2 to make their function more clear. I also made a wiki to go over some of the tricky setup details, so please check that out.

Improved - Build/release pattern
In v1, the action performed all of its steps on the source branch of a project. Each update, build, and push to the source branch added garbage commits to the history of what could have been a working branch for some people. Now the action builds releases on a separate branch to help clean that up.

New - TEST MODE
Test mode runs a separate set of scripts (instead of the normal action) and verifies that your setup is correct. If you use test mode you're likely to spot most problems with your action config before you run it for real.

Fixed - Git config
Previously, git config was always set by this action. Now it occurs only when the git config values haven't already been set by other workflow steps. This is to allow work with other actions and avoid setting conflicting config values. Bonus: Now you can do neat things like setting up GPG commit signing with other actions like this -- https://github.com/aormsby/Fork-Sync-With-Upstream-action/wiki/GPG-Signing (link is from another one of my actions, but you'll get the idea)

Known Issue - Can't use shallow clones
Trying to get proper merges when using shallow clones has been a huge problem. Gotta checkout with fetch-depth: '0' for this action to work properly. See Git Shallow Clone Challenge! for details, and help me figure out what to do about this!

v1.2-beta

• Default values removed for input vars with required: true. These must now be set explicitly in your workflows.

  • deploy_directory - Name of Hugo build output folder (path from root directory), Hugo's default is "public"
  • build_branch - Repo branch used for site build

• The 'deploy_branch' input var is still set required: false since some users will not deploy to submodules. However, the default value has been changed to 'main' to match Github's changes to a new repo's default branch name.

v1.1-beta

security updates - 'core' module updated to 1.2.6

v1 beta

An action for Hugo websites. Build your site from whichever repo branch you choose and deploy to a GH-Pages repo. This action supports deploying to the main site repo or to a repo submodule. No extra work is needed for submodule deploys. It's intended use is to simply automate Hugo site builds.

Functional and tested, but tested in a limited capacity. Please be aware issues may arise.