I want the equivalent of 'lint' or 'ruff' for GitHub repos. Does the repo name match a pattern? Are the right issue labels set up? Et cetera. I can write a script to do this, but if it already exists, a pointer would be welcome: how do you manage the 780 repos your org has?
Thanks to @henryiii for showing off the web hosted version of Scientific Python's "Repo-Review" tool recently, which also has a CLI, and does just that, running a repo against certain established rules of best practices (tied to their documentation).
But I think the CLI also supports writing your own rules as plugins, or requesting or contributing back upstream. Could be a good framework for checking your repos against a list of such conditions!
@gvwilson OpenSSF Scorecard (https://securityscorecards.dev/) might cover a few of the things you're looking for (or things that you're not but you maybe should be). I've never thought about a project configuration linter, though. The TODO group has something kind of in that direction: https://github.com/todogroup/repolinter but it's more about the code than the repo itself.
I'm not aware of anything that solves your problem directly, but I'd be interested in contributing to a solution if you decide to build one.
Add comment