Closed ghost closed 8 months ago
Hmm, that's weird. Using the default token explicitly shouldn't change anything, since that's the default value being used...
Are you restricting token permissions anywhere else in your workflow? Also, please check your actions settings at https://github.com/inspire-labs-tms-tech/zenbridge/settings/actions, make sure that you're not restricting the action from accessing the repo
@EndBug thanks for the reply! I ended up shuffling our workflows around, but for some reason, I did not get the error when using:
# ...
on:
push:
# ...
Maybe push
has different permissions? The error then came immediately back if all I did was switch back to:
# ...
on:
pull_request:
# ...
Are you running this on every kind of pull_request
event, or just on open, close, ...?
Anyway, I think this is the call that is causing the error, because it's run only when a pull request is used
Are you running this on every kind of
pull_request
event, or just on open, close, ...?
@EndBug I was running it only on pull_request: opened
and reopened
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is still happening :)
Describe the bug With a simple setup using the example in the README, I am still getting a 403 error.
To Reproduce
Edit: I also tried running setup node first, too, but this still fails:
Expected behavior 403 should not occur with the token; is it properly being passed?
Screenshots
Additional context Add any other context about the problem here.