> The get and post routes both go to the same function due to the problem I was texting you about this morning. The initial call to the gitHubLoginPost function is a post, but then when the gitHub oAuth authorization returns to our web app, it is completed as a get, and therefore the post route that I had was not catching it, even though it was the same URL. Would we be able to change the initial call to the login function to a get? If so we can make do with just the one route. 

I guess the reason I pointed this out is that I figured that a user going to this URL after clicking the login button functioned differently than GitHub going to this URL. To me, there seems to be two distinct, logical sections here, suggesting to me that this should be broken up into different methods.

What have you found from other people using OAuth2? Did anybody else choose to structure their code like this? I'm challenging your decision because I want to understand it, not because I think it's wrong. It just seems strange to me.