-
Suggestion
-
Resolution: Fixed
Github now provides OAuth tokens as an authentication mechanism for pulling/cloning repositories. Do you have a plan/timeline for implementing this?
Currently, the only way to deploy private repositories onto platforms like Heroku (that don't allow private SSH keys) is to explicitly use username/password credentials, which aren't easily revokable and pollute logs & source control with credentials (which is bad!).
Thank you, @erikvanzijst. Now we can hook up our internal CI system. One question, though: do I need a token pair for the Team account to see the team's private repositories? It appears I can only see the public repositories (including my own) with the token pair. I don't see an option to enable that in the token configuration.