mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #739] Issue: Dockerfile context relative path #466
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#466
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 @ryuheechul on GitHub (Jun 18, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/739
I experience this with such action below
it appears to use https://github.com/mikefarah/yq/blob/master/Dockerfile even though it points to
https://github.com/mikefarah/yq/blob/master/github-action/Dockerfile via https://github.com/mikefarah/yq/blob/master/action.yml#L15.
Probably somethings should be done in this line below to fix this issue.
github.com/nektos/act@a9fe038347/pkg/runner/step_context.go (L472)System information
Expected behaviour
use the right context path (
github.com/mikefarah/yq/github-action(/Dockerfile)) to build the imageActual behaviour
use the wrong context path (
github.com/mikefarah/yq(/Dockerfile) to build the imageWorkflow and/or repository
workflow
Steps to reproduce
actoutputLog
Additional information
About the usage of the
yqaction, not only works in Github,you can find the spec here as well, https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsimage.
@github-actions[bot] commented on GitHub (Jul 19, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@mattwynne commented on GitHub (Jul 23, 2021):
I'm seeing this too