sha deployments

[GrantBirki]

SHA Deployments

This pull request enables users of this Action to target specific SHAs for deployment. The most common use case for this is "rollback" deployments.

You can now run .deploy <sha> to <environment>

Where <sha> is either a full sha1 or sha256 hash

Example:

.deploy b69ba12504020c9067abe680c1dc28191d4c9be3

or

.deploy b69ba12504020c9067abe680c1dc28191d4c9be3 to production

For example, if you have an edge case where your branch deploy failed, and your .deploy main (base branch) failed you may want to revert to a previous commit. You can now do this with .deploy <sha> and the branch-deploy Action will use this as your target sha to be re-deployed.

In order to use this new feature, you must set the following input option:

- uses: github/branch-deploy@vX.X.X
  id: branch-deploy
  with:
    allow_sha_deployments: "true" # <--- this option must be "true"

The reasoning for this is that deploying to a sha can be a dangerous and potentially unsafe option, so it is disabled by default. More details about why this is an issue can be found here

---

related: #211, #213