Custom repo input and checks

[rpodcast]

Writing my thoughts now before hitting 🛏️

• We talked about letting the user enter the name of a GitHub repository which has issues being worked on at the particular unconf, with the added bonus of having this additional repo magically added to the existing list of repos being scraped in the app
• Before adding the user-entered repo name to our master list of repo names, we should do a quick check to make sure that repo indeed has issues tagged with the unconf label. Otherwise someone could just add a boatload of repos and gummy up our system, right?
• We could use a simple call to projmgr::parse_issues in the observeEvent call of repo adding click and pop-up an alert box if that repo does not have any unconf issues. But if it does, we proceed forward with the repo addition to the existing repo list.