Closed christian-bromann closed 3 years ago
Hmm, the only token scope you should need is repos
, do you have that scope set?
Closing this due to age.
I had the same issue and after much searching was directed here. I have cloned this repo into our GH Enterprise server so I can use it there as we can't use external repos on our internal system.
This error took me a while (longer than I'd like to admit) to work out. It turns out that all I had forgotten was to give the machine user, that is the owner of the token, permission to write to the repo I was trying to trigger the event on.
It is not mentioned in the README but I am sure it is the cause of this 404, because the default response for an end point in GitHub that you are not authorised to access is 404.
Hi @MartinLesterSynamedia, I have the same issue. How did you give permissions to write to the repo you trying to trigger the event on?
Thank you
Ok found it, my mistake was giving the url of the repo and not his name.
I have setup the action as following to trigger another workflow after the pipeline:
this fails as follows:
Am I missing an important token scope here?