-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
local js action fails (uses: ./) #185
Comments
Hey, I had the same issue, but already posted my solution in #228. You need to provide the |
Sorry if this belongs in a new issue, but I'm experiencing a very similar problem in a similar situation. I'll be glad to open a new issue, if that would be better.... It looks like For instance, I have a workflow referencing a local action.... - name: Auth0 deployment
uses: ./.github/actions/auth0-deploy And my action.yml file in that directory looks like this: name: auth0-deploy
inputs:
prod-branch:
description: Name of the branch to consider "production". Default is "master".
required: false
runs:
using: node12
main: 'dist/index.js' When I run locally, I get the same kind of stack trace:
However, this configuration is valid per the GHA documentation, and the workflow runs successfully on GitHub. |
Issue is stale and will be closed in 7 days unless there is new activity |
Can this be reopened? I've confirmed this use case breaks for me: - name: checkout foo
uses: actions/checkout@v2
path: .github/actions/foo
- name: use foo
uses: ./.github/actions/foo Gets
should resolve to
|
Fixes nektos#185 Signed-off-by: Javier Romero <root@jromero.codes>
Fixes nektos#185 Signed-off-by: Javier Romero <root@jromero.codes>
Fixes nektos#185 Signed-off-by: Javier Romero <root@jromero.codes>
Fixes #185 Signed-off-by: Javier Romero <root@jromero.codes>
When developing a new JS action, I like to create a workflow within the same repo so I can test various use cases. In such a case, I reference the local action with
- uses: ./
as defined in the documentationUnfortunately, it fails with the following error:
It does work if I move the action code in an
action
subfolder and use it with- uses: ./action
.This can be reproduced with the sample hello-world-javascript-action, you just need to add a basic workflow.
The text was updated successfully, but these errors were encountered: