stale info error when specified branch doesn't exist but a tag with the same name exists about create-pull-request

[peter-evans]

Hi @stevemao

Thanks for raising this issue.

The simple workaround for this is just to rename the branch input to something that doesn't clash with an existing tag. (Which I can see you have already done 👍 ).

Also, in general I would advise not creating branches and tags with the same ref name. It does create ambiguous situations for git and makes operations more complicated.

As for whether the action should actually support this situation, I'm leaning towards not attempting to add support for it because the workaround is so straightforward (and best practice, in my opinion). I've only had a couple of users ever bump into this kind of issue where tags clash with branch names, so it's pretty rare I think. To support it, and other similar cases where tags clash with branch names, I think it would make the git operations in this action quite a bit more complicated.

I'm going to close this issue as "won't fix," but I might reopen it in future if many users are running into this issue.

[stevemao]

Yes exactly what I thought. And I did.

Perhaps add this and related issues to the faq?

FYI: There are new commands such as git switch which only works on branches but not tags.

Thanks for the detailed explanation!