Can this work with Branch Protection?

[kroese]

I have my master branch protected so that it only accepts pull request and not normal pushes.

The other tag actions I tried could not work with this, so I am wondering if this one can? And if not, is there some workaround possible? For example by adding the tag push to the current pull request for example?

[kroese]

Okay, I just tried it, and got the familar cryptic message:

fatal: cannot lock ref refs/tags/***.***': Unable to create
/github/workspace/.git/refs/tags/***.***.lock: Filename too long

This has nothing to do with any filename being too long, because if I disable Branch Protection it works.

So is there a way to make this work?

[sbe-arg]

Can you share your workflow config and runner logs?

[kroese]

@sbe-arg It's just with the default workflow config from the readme, and the runner log doesnt contain anything more than the above error.

Branch protection disables pushing code directly to the branch, so in that way it makes sense that pushing the tag will fail too.

But on the other hand: I am able to create tags and releases on a protected branch just fine by using the Github REST API. So it seems the protection only applies to tags created via git push and not to tags created via a REST call.

So it would be nice if this action would fallback to using the API method when it detects the current method does not work.

[sbe-arg]

Have a look we don't do a git push https://github.com/anothrNick/github-tag-action/blob/1.62.0/entrypoint.sh#L236-L258

Share the logs please.

I personally use this in many many repos with extreme branch protections and the tags work like charm.

[sbe-arg]

More relevant information #210

[kroese]

@sbe-arg Okay, I discovered the source for my issue. And you were absolutely right that it has nothing to do with Branch Protection. I was a bit mislead because it worked fine in another repo where I did not have Branch Protection, but it turned out it was a problem with the contents of the variable I used for CUSTOM_TAG (which also was different between the two repos). My mistake, sorry.