We built this internally and it is a godsend, particularly as you can then start layering on remediation advice for the developer.
Nobody should have to Google an error your organization fixes 100,000 times a year.
Nobody should have to Google an error your organization fixes 100,000 times a year.
Rough shape of the things you can do:
Your build failed the linter:
foo.rb line #123 Don’t use hashrockets (=>) use {x: “something”}
Consider setting your IDE to lint on save. Instructions here: ...
This look wrong? Correct slack channel to raise in: #foo
Your build failed the linter:
foo.rb line #123 Don’t use hashrockets (=>) use {x: “something”}
Consider setting your IDE to lint on save. Instructions here: ...
This look wrong? Correct slack channel to raise in: #foo
Almost all toolchains assume that software development is a single player game. This is catastrophically wrong.
You should cheat the heck out of your local setup by embedding knowledge of how your organization works: where do questions get asked, what are local expectations, etc
You should cheat the heck out of your local setup by embedding knowledge of how your organization works: where do questions get asked, what are local expectations, etc
A feature of systems like this that I really like is composability, because composability is leverage.
e.g. We had that working for CI doing lint of Ruby but not for lint of a particular React project. I got frustrated about that and spent 10 minutes Googling. Fixed forever.
e.g. We had that working for CI doing lint of Ruby but not for lint of a particular React project. I got frustrated about that and spent 10 minutes Googling. Fixed forever.
