[GH-ISSUE #305] entry point in action.yml should be relative to action.yml not cwd/project-root #215

Closed
opened 2026-03-01 21:41:20 +03:00 by kerem · 4 comments
Owner

Originally created by @jsg2021 on GitHub (Jul 11, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/305

First, I want to say this project is amazing. It has sped up my workflow testing/debugging so much! Thank you for this!

Anyways,
I was using this to test a private action that is hosted in a subdirectory of my project. When I came across this bug.
I didn't think anything of it and thought my entry point was just wrong and updated it to cwd/project-root relative and moved on... however when I pushed it to GitHub, it failed when looking for my entry point.

ex:
<project>/actions/sync/action.yml
with:

runs:
  using: 'node12'
  main: 'src/index.js' # when running local this has to be 'actions/sync/src/index.js'

In my <project>/.github/workflows/test-sync.yml workflow:

  - name: Sync
    uses: ./actions/sync
Originally created by @jsg2021 on GitHub (Jul 11, 2020). Original GitHub issue: https://github.com/nektos/act/issues/305 First, I want to say this project is amazing. It has sped up my workflow testing/debugging so much! Thank you for this! Anyways, I was using this to test a private action that is hosted in a subdirectory of my project. When I came across this bug. I didn't think anything of it and thought my entry point was just wrong and updated it to cwd/project-root relative and moved on... however when I pushed it to GitHub, it failed when looking for my entry point. ex: `<project>/actions/sync/action.yml` with: ```yml runs: using: 'node12' main: 'src/index.js' # when running local this has to be 'actions/sync/src/index.js' ``` In my `<project>/.github/workflows/test-sync.yml` workflow: ```yml - name: Sync uses: ./actions/sync ```
kerem 2026-03-01 21:41:20 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Sep 12, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:691363606 --> @github-actions[bot] commented on GitHub (Sep 12, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

@jsg2021 commented on GitHub (Sep 12, 2020):

no. you're stale. 😜

<!-- gh-comment-id:691367012 --> @jsg2021 commented on GitHub (Sep 12, 2020): no. you're stale. 😜
Author
Owner

@github-actions[bot] commented on GitHub (Jan 8, 2021):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:756474893 --> @github-actions[bot] commented on GitHub (Jan 8, 2021): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

@github-actions[bot] commented on GitHub (Feb 20, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:782474091 --> @github-actions[bot] commented on GitHub (Feb 20, 2021): Issue is stale and will be closed in 14 days unless there is new activity
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#215
No description provided.