Closed lassik closed 4 years ago
I wasn't able to add new builds on Docker Hub when the bot was just a member. But I'm sure there's a way around it somehow, I'm just not sure how. Their instructions are unclear. Feel free to experiment.
Whenever a new implementation (i.e. git repo) is added to Docker Hub, it sends email that says the bot added a Docker Cloud Build key to our repos. That's probably why it needs to be Owner. But why does it need to add the key, given that our repos are public?
Probably in order to get notified of PRs and commits and build them instantly, right?
Probably in order to get notified of PRs and commits and build them instantly, right?
Yep.
Still haven't found a way around giving owner permissions to the bot, so closing. Feel free to re-open if needed.
scheme-docker-bot
currently has the "Owner" role on the scheme-containers GitHub organization. Would it be keep working if we downgraded it to "Member"?