New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$RESOLVED_VERSION not expanded when set via action input #1048
Comments
Maybe but what's wrong with using name-template? |
Nothing wrong with using ...
with:
name: "Project A $RESOLVED_VERSION"
... repoB has the workflow ...
with:
name: "Project B $RESOLVED_VERSION"
... BTW: I tried to achieve that with env variables, by passing the project name to the base file, but that doesn't working (#847). Actually for our needs using |
Right make sense, would welcome a PR :) |
Sure, I hope I find time. |
You should have access to $REPO and $OWNER maybe I made a mistake and did not allow it to be expanded in name-template and tag-template most likely for tag-template it should lowercase or simply not be possible? |
(Closed by accident) I just tried again, That's what I see in https://github.com/playframework/twirl/releases right now ( That's what I saw a couple of minutes before adding the So we do have access to |
Exactly |
Using the
name
input:the release draft will be named
$RESOLVED_VERSION
, which obviously is not what I expected.However inside the config file
the release draft will correctly be named with the version, e.g.
1.0.0
.Now, the
name
overrides thename-template
:I expect both configs behave identically, I would have guessed variable expansion takes places after the override happened, so it shouldn't matter where the config string came from.
The text was updated successfully, but these errors were encountered: