Closed maxirmx closed 1 year ago
Added as RNP_CI_PAT_TOKEN
.
@ronaldtse
It says token has insufficient permissions
Could you please recreate it with public_repo scope as shown below:
That worked in my tests. Thank you
@maxirmx the current token already has the said permission. Could it be that the token name is not set correctly and hence reading an empty token?
With this token GHA triggers php-rnp but fails to trigger ruby-rnp. So the issue is not related to the token or rnp workflow.
Also it triggers ruby-rnp from my personal workflow using my personal token so the issue seems not to be related to ruby-rnp workflow either.
Now it looks like a mistery
With your latest hint I found out the the Ruby-RNP repository did not provide the CI user with write permissions, and it’s now fixed. Hope it works now!
Thank you, @ronaldtse It works !
In order to trigger ruby-rnp workflow from rnp master workflow Personal Access Token is required It shall be created in this (ruby-rnp) repository and added as a secret to rnp repository (https://github.com/peter-evans/repository-dispatch#token)