Fixes #309

[druskus20]

Summary of changes

Breaking Changes

NO

Since I added a new argument (FORCE_WITHOUT_CHANGES_PRE), there shouldn't be any.
Alternatively, we can use FORCE_WITHOUT_CHANGES for prereleases as well, which would imply a breaking change.

How changes have been tested

I've tried the fork on a private repo. It works as expected. The changes are also minimal so they should be fine.

List any unknowns

[sbe-arg]

I like it but the releases are broken and we don't know why and I don't have time to debug. see failed releases https://github.com/anothrNick/github-tag-action/actions/workflows/main.yml

[druskus20]

@sbe-arg
I just ran the CI myself on my fork and it worked. I needed to push to master for "Version Bump" to activate, due to the nature of the CI job. I later force pushed, removing my tests from the history of this PR, but they still show up on https://github.com/anothrNick/github-tag-action/actions. My apologies.

In any case: the Bump CI job does work on my own repo, so changes to the yaml manifests should not be needed. It might be worth checking if "read and write permissions" are enabled?

PD: For my specific usecase a release is not needed, I will pin the commit hash regardless.

[sbe-arg]

Any of those repo config changes are only allowed by @anothrNick wich has been tagged in this issue/problem before.

Also is unclear why we suddenly started having this problem.

Its hard to "test" this myself is something on hands of @anothrNick to fix atm 🤷‍♂️

[anothrNick]

Settings all look right on this repo, I've also confirmed that the latest commit on master, as well as the other configuration options within the workflow, work fine in another repo...

I'll keep reading around a bit today, really not sure whats going on.

[anothrNick]

Made a change to our workflow using pull_request_target - https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target

That would explain why it is working in contributors' repos but not when its PR'd here.

I also wonder if this just started popping up due to timing with:

• Optionally pushing tag with git vs. API
• The permission changes for workflows

Either way, I'm going to merge this PR and see if it works.

[anothrNick]

@druskus20 can you resubmit this PR? I didn't update the event_name check in the job