That’s where I was heading as well. The rubocop is perfect candidate to get extracted to github action, as the response is imediate, so it serves instead of annoying hound (notify me in matter of minutes, that i need to reformat and thus I am more likely to do it right away).
That’s why I’m inclined for easy solution. Shared config in foreman core, that offers basic cops, that we think all the plugins should use is what my PR would offer.
The url referenced cop is actually downloaded locally and checked only once in a while (can be include in git), probably not hard failing if no internet connection available.
I agree that versioning of it can be an obstacle, but on the contrary it doesn’t change as often.
Plus it’s not as hard to move to a gem, once we see that the versioning is an real issue.