Add New Fields to Repos

[DanielJDufour]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] I'm supposed to add an ability to sort the browse projects page and search results page, by a lot of different options, including some that aren't returned by the API yet: - Forks - Contributors - Issues - Open Tasks - Pull Requests - Stars - Watchers

Describe the solution you'd like A clear and concise description of what you want to happen. I'd like to see this information attached to each repo returned by the /repos endpoint

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. I will leave it up to you over what is the best format for this. Perhaps, you can consider adding nested properties like creating a github_info object that stores these values and that you attach to each repo.

Additional context Add any other context or screenshots about the feature request here. I'd ask @jlow81 , what the priority is here. Basically, I can sort by any of these values until they're adding into the backend.

[DanielJDufour]

I added some labels. Feel free to remove or replace them if I got them wrong :-)

[Nosferican]

That information could be queried directly using the GitHub API given a remote on GitHub. The remote should be good enough. Those interested could query the information from GitHub directly.

[froi]

The issue with making this query on the spot is always rate limits. The reason we did this in the first place was to avoid managing this. We also wanted this data to be "standard" across the repos that were in Code.gov. This also affected the UI of Code.gov, at least when this was made ...