developer model now validates on uniqueness of github username. Given that we are using GitHub Omniauth for verification, this should never actually happen -- but having a db-level validation will protect the db from being polluted in case of an uncaught error
remove githubdataloader module from application controller. functionally better fit for developer model, not controller.
developer model now can access github data on repos and profile info
post route for developer repositories now exists. currently rendering nothing
developers controller now has repositories route, which returns a given developer's repositories scraped from github. intentional impersistence on db side
writing tests for developers repositories route
deletes feature test
repositories controller action now renders in JSON
creates basic repositories partial
adds repositories partial to developers show page
developers show controller now scrapes for git repos
return all repos now links to GUI url, not api url
button in repositories partial now routes to project controller
all tests calling the github api marked as pending. we just found out about github's rate limit
user can create projects from developer show page
githubdataloader now returns repo owner
githubdataloader authorizes on request, now can make 5000 requests an hour.
Merge pull request #13 from dmill/fuck-your-rate-limiting

removing rate limit issues
removes pending designation from api-related tests
file now conforms to git api test standards