You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this action is in a workflow triggered by workflow_call:, it does not have access to secrets.GITHUB_TOKEN like it should... I believe this is because you are using it as an env variable rather than just a parameter to pass into your action.
A clear and concise description of what the bug is.
Make a repo with this action in a workflow_call:
Reference that action with uses in an action from a different repo (same org/account)
Witness error.
It should run as defined by GitHub
The text was updated successfully, but these errors were encountered:
* ci(release): 👷 add github actions workflows
* ci: 👷 restructure CI workflows
- the action-semantic-pull-request action is not able to run as workflow_call
- see amannn/action-semantic-pull-request#232
- see amannn/action-semantic-pull-request#271
* ci: 👷 run push workflow only on push action
- rewrite the workflow as amannn/action-semantic-pull-request@v5 cannot run on push
- do not run push workflow on pull_request action
- do not run push workflow on pull_request_target action
* ci: 👷 remove secret GITHUB_TOKEN
- prevent variable name collision with system reserved name
* ci: 🚧 remove secret GITHUB_TOKEN
* ci: 🚧 try to get the changesets setup
* ci: 🚧 fix unknown commits issue
* ci: 🚧 fix unknown package
* ci: 🚧 fix local action run
* ci: 🚧 simplify workflows
If this action is in a workflow triggered by workflow_call:, it does not have access to secrets.GITHUB_TOKEN like it should... I believe this is because you are using it as an env variable rather than just a parameter to pass into your action.
A clear and concise description of what the bug is.
Make a repo with this action in a workflow_call:
Reference that action with uses in an action from a different repo (same org/account)
Witness error.
It should run as defined by GitHub
The text was updated successfully, but these errors were encountered: