Ok fellas, I took another pass at this with some help from @pepopowitz and have pushed up how I think this should go down. @orta brings up a good point re: making a ton of issues and the current implementation does nothing to ensure there isn't already an issue opened for this violation.

But I like the direction it's taking and wanted to get something up to keep the momentum going on this sucker.

making a ton of issues and the current implementation does nothing to ensure there isn't already an issue opened for this violation

Because you're using danger.github.utils.createUpdatedIssue it won't create a dupe

Oh that's great news @orta, did not know that!! ❤️

So it looks like we're just blocked on the rate limiting, right? danger.github.api returns an Octokit instance for the v3 REST endpoint (I think), and for authenticated requests, the docs describe a rate limit of 5000 requests/hour. So I think we might actually be okay? Artsy has 123 private repos FYI.

@orta does that reasoning hold?

Yeah, I think it might even be per-repo on the GitHub app

if folks are happy, this will still need hooking up in the peril settings json though

Ok, did some final polish on this with @ashfurrow and I think this is ready for final review!! ❤️

Sorry to butt in late, might be worth making that the issue comment give and example reason so peeps can C&P into their READMEs and edit it (to understand the formatting)