Support custom target_commitish value (#76)

* Make target_commitish configurable

* Store compiled action for testing

* Add target_commitish to metadata

* Allow override of target_commitish for updating

* Print commit usage

* Improve message for commit usage

* Update draft releases too

* Revert "Update draft releases too"

This reverts commit ff30f8e.

* Integrate latest changes from upstream.

README.md

@@ -181,6 +181,9 @@ attempted first, then falling back on `body` if the path can not be read from.
 💡 When the release info keys (such as `name`, `body`, `draft`, `prerelease`, etc.)
 are not explicitly set and there is already an existing release for the tag, the
 release will retain its original info.
+=======
+
+💡When providing a `body` and `body_path` at the same time, `body_path` will be attempted first, then falling back on `body` if the path can not be read from.
 
 #### outputs
 

action.yml

@@ -37,6 +37,9 @@ inputs:
   target_commitish:
     description: "Commitish value that determines where the Git tag is created from. Can be any branch or commit SHA."
     required: false
+  target_commitish:
+    description: 'Commitish value that determines where the Git tag is created from. Can be any branch or commit SHA.'
+    required: false
 env:
   "GITHUB_TOKEN": "As provided by Github Actions"
 outputs: