Ran into this today. As it stands, non-admin machine users don’t seem to serve any purpose(?).
Kind of related, if Drone continues to operate as a OAuth app, it would be best to always use the token of the repository owner for all operations and also display the owner aka who activated the repository.
When the owner of a repo leaves an org we are sometimes left with a dangling repo because their token is no longer valid for repos in the org, but it’s a hunt to track down who it is and get someone else to
chown the repo.
Having the owner name displayed would greatly help, or even being able to filter the list of repos by owner name.
Otherwise another approach after fiddling around with Circle CI is they seem to associate each repo with multiple users, so that as long as someone’s credential works, the GH API interaction is successful. This means they require each user who wishes to see that repo to “activate” it by adding it to their list of “watched repos”.
While it’s another step for the user when getting started, it does alleviate the “someone left the team and the repo stopped building” issue, since it will just use the next user’s token.