Error when using branches with floating numeric names

[fernando-pcg]

Hello,

Error when using branches with floating numeric names

In my projects, branch names of the floating type are used, for example 15.0, 16.0, but the parameters do not allow this, when using these numbers it does not consider the .0 and it is not possible to change these names, so it does not find the branch, I also tried to put these names inside quotes but it gives another error.

Steps to reproduce

Create the action with a branch with a floating name.

If this issue is describing a possible bug please provide (or link to) your GitHub Actions workflow.

[peter-evans]

Hi @fernando-pcg

This might be an issue with the yaml parsing on the runner. Could you try setting the base like this and see if it fixes it:

base: "16.0"

[peter-evans]

I also tried to put these names inside quotes but it gives another error

I just saw you already tried that. Could you share that error/log.

[peter-evans]

I've spotted another issue, which is probably the "another error" you mentioned. Setting the branch like this will not work.

branch: ${{ github.ref_name }}

Please see here for an explanation: https://github.com/peter-evans/create-pull-request/blob/main/docs/common-issues.md#create-using-an-existing-branch-as-the-pr-branch

[fernando-pcg]

Hi @fernando-pcg

This might be an issue with the yaml parsing on the runner. Could you try setting the base like this and see if it fixes it:

base: "16.0"

This is the error I get when trying with '16.0',
I can try it with the double quotes, but I guess it would be something similar, I'll try it anyway

Edit: Yep, got the same error

[peter-evans]

@fernando-pcg Using quotes is the correct way to avoid the original error you had. So please keep the quotes. 👍

The problem now is what I mentioned in this comment: #3493 (comment)

[fernando-pcg]

@fernando-pcg Using quotes is the correct way to avoid the original error you had. So please keep the quotes. 👍

The problem now is what I mentioned in this comment: #3493 (comment)

Get it, im gonna look for a work around