403 on APIs to activate repo


I am suddenly started getting 403 http status code when i am trying to activate a repo

I have also tested now using cli and the command shows “client error 403: Administrative access is required.”

But when i do “drone user info xxx” which is working fine, a command which requires admin access

Seems like you need admin access on each repo to activate it. Strange, i thought it would use the credentials of github authorized oauth app we created and not the users credential

Creating webhooks requires admin access

This is the expected behavior when using oauth. The user authorizes the application (drone) to perform actions on his/her behalf. Drone cannot perform actions on behalf of the user unless the user has the appropriate permission levels within github.

1 Like