3 ms·
This looks fine if you're a single developer working on a (relatively) small project, but what happens when you grow to two developers? Or you hand off the proj
by bigfrakkinghero 14y ago
This looks fine if you're a single developer working on a (relatively) small project, but what happens when you grow to two developers? Or you hand off the project? At that point shouldn't the API registration be tied to the application and not the developer?
That said, it's probably more important to lower the initial barrier for entry to drive adoption.
- speg 14y agoIs there anyway to tie it to the team instead of just the developer?
- mh- 14y agolooking at the (GitHub) API.. doesn't seem like it http://developer.github.com/v3/oauth/#scopes http://developer.github.com/v3/oauth/#scopes edit: hmm, now I'm not sure. looking at my employer's organization (that I have the 'owner' role on) I can certainly authorize apps via GitHub.com.