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.
What's the purpose of this logic? It doesn't look like there's a `user_id` field on repo, and I don't think we'd really care about that anyway.