Repo Depot!

## Description and Impact
Extends functionality by allowing all of an organization's repos be watched

## Deploy Plan
Nope

## Rollback Plan
* To roll back this change, revert the merge with: `git revert -m 1 MERGE_SHA` and perform another deploy.

## URLs
> Links to bug tickets or user stories.

## QA Plan
> Fill in scenarios below. Review [QA Best Practices](https://source.sportngin.com/page/show/1227795-qa-best-practices).

#### Risk Level:
- [X] Low
- [ ] Medium
- [ ] High

This is really just a intermediary pull_request, it doesn't really do much as of yet, just see how the code looks.
Couple of things you can do here:

First off, you should really turn the first line into scopes on your models:

 ```ruby
# Hubstats::PullRequest
scope :last_two_weeks -> { where(["closed_at > '%s'", 2.weeks.ago]) }
scope :closed_at_desc -> { order("closed_at DESC") }

@pull_requests = Hubstats::PullRequest.last_two_weeks.closed_at_desc
```

For a couple of reasons:

1.  SQL will **always** be faster then ruby at sorting, so using `.order` is very much prefered.
2.  Scopes dry up the code a little bit and allow you to reuse the code a bit, as well as make changes in just one spot.
3.  It frankly is just easier to read from a controller perspective.


With the `@users` one, you probably could just include the sorting in the method itself.  Again, you probably can do this via SQL, so that would be preferred.