-
Notifications
You must be signed in to change notification settings - Fork 124
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
Regression on token permissions #52
Comments
Fyi - I'm seeing the same behavior when trying to trigger a workflow within a single repository without passing a github token. |
Actually, I was able to get this working by providing the following permissions to me action:
|
thanks @jamiezieziula, can confirm your fix: name: Trigger release-runners.yaml daily
on:
schedule:
- cron: "4 2 * * *"
workflow_dispatch:
jobs:
trigger-build:
+ permissions:
+ actions: write
runs-on: ubuntu-latest
steps:
- name: Invoke workflow
uses: benc-uk/[email protected]
with:
workflow: release-runners.yaml
- inputs: '{"push_to_registries": true}' # ERROR: For 'additionalProperties', true is not a string.
+ inputs: '{"push_to_registries": "true"}' |
@benc-uk does this warrant an update of the README? |
I'm seeing the same behavior, only on I will try adding the permissions section and report back. Update: Now working for dependabot PRs! |
@dersimn thanks for the suggestion, but I already have that enabled for every repository in our org. And actually to update my last comment. It only works for org admins, and dependabot. It does not work for other members (who have write permission) on a repo. |
Hi 👋
Just tried out your action (thanks 💥) and didn't get it to work (logs):
Error: Resource not accessible by integration
The yaml is pretty straight-forward:
Maybe something changed on gh side?
The text was updated successfully, but these errors were encountered: