mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #108] Matrix variable used in job name not expanded #70
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#70
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @davidalger on GitHub (Feb 27, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/108
Attempted to execute the workflow found here: https://github.com/davidalger/docker-images-php/blob/master/.github/workflows/build.yml
The result was the following (in many more colors than can be printed here):
Since the container name is being derived from the job name, the job completely fails. The job name should render out (for example) to "[Docker Image CI/PHP 7.3]"
@cplee commented on GitHub (Feb 27, 2020):
fix is available now in master, will be in next release
@davidalger commented on GitHub (Feb 27, 2020):
Awesome. Thank you!
@cplee commented on GitHub (Feb 28, 2020):
available in
v0.2.5@alexkli commented on GitHub (Mar 4, 2020):
@cplee I get the same issue with
v0.2.5:Here is the Github action yaml.
@alexkli commented on GitHub (Mar 4, 2020):
If I try to give my builds a
namelike the OP did, it doesn't help:Result:
@alexkli commented on GitHub (Mar 4, 2020):
🎉 It works if I use
node_versioninstead ofnode-version, to bypass the ReferenceError:Result:
@cplee commented on GitHub (Mar 4, 2020):
Nice troubleshooting @alexkli
OK to close again?
@alexkli commented on GitHub (Mar 4, 2020):
I think there are still two issues that could be fixed/improved:
name(my original yaml, perfectly fine in github)-in variable names@cplee commented on GitHub (Mar 4, 2020):
Will leave open for first bullet point. Second one is covered by #104 which I closed as wontfix 😞