The permissions form is confusing, but I don't think this is true, I've definitely got Travis at least setup on single organizations. If something weird has changed and this is true, we could also create an "XSF Bot" account or something and then it's not a problem because the bot only has access to XSF repos.
Alternatively, just add GitHub actions to whatever repo needs them. Those definitely only have access to that repo (unless you give it access to others). On Tue, Jun 16, 2020, at 13:12, Jonas Schäfer wrote: > Due to the messed up permission model of GitHub, all of them (I can’t > test travis because I signed up with them a long time ago, Circle CI > does, GitLab CI for GitHub does, Docker Hub does for newly added > repositories; Drone seems to require infrastructure we don’t have or > want to maintain on the iteam side) seem to require full write access > to all repositories whichever account is used to set them up has > access to or will ever have access to, public and private. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
