Support getting GitHub API v2 tokens when configuring a repository.
Review Request #3076 — Created April 24, 2012 and submitted
Support getting GitHub API v2 tokens when configuring a repository. GitHub is soon deprecating its older APIs in a switch to their v3 API. As part of this, they have removed the API tokens from the accounts page. However, they just today announced an API for getting these legacy tokens. This change adds a "Get your API token" button that prompts for a password and then fetches the API token for the user and populates the field. With this, people should be able to set up new GitHub repositories again.
Tested with both valid and invalid credentials.
Turns out GitHub doesn't in fact ignore the Same Origin policy. It does for registered applications, and someone registered something with "localhost:8080", which is why it worked here, but it failed for other domains. Now there's a URL that fetches the token, basically working as a proxy.
Revision 3 (+119 -5)