Yeah, one or more deployment accounts is the approach I've seen most "in the wild". Machine users[1] with tightly scoped access to a collection of repos. Access

Yeah, one or more deployment accounts is the approach I've seen most "in the wild". Machine users[1] with tightly scoped access to a collection of repos. Access can then be managed through the relevant Read-only GitHub team. [1] https://developer.github.com/guides/managing-deploy-keys/#machine-users https://developer.github.com/guides/managing-deploy-keys/#ma...