gewenyu99

A journal reaching top of Hackernews? What is this?

What's the point here over like just hitting rerun and maybe just hitting rerun again?

I mean I feel like you shouldn't have a bunch of flaky tests anyway if you're writing them properly

Yes, we sponsored them because we have a commercial product that uses ESLint and we want to contribute back to open source. I don't see why this is an issue.

We also wanted to show them our metalinter, which we believe has genuine use cases in open source. That's why it's free for open-source repos (all public repos).

The CLI tool is also just free for everyone, for ever.

Us, from Trunk.io: "Oh look we're at the top of Hackernews! Oh wait it's not us"

Looks better these days than beginning of year ngl

Well, we built Trunk Check to address some of these issues. Maybe it'll suit your org better.

- We support hold-the-line: we only lint on diffs so you can refactor as you go. Gradual adoption. - Use existing configs: use standard OSS tools you know. Trunk Check runs them with standardized rules and output format. - Better config management: define config within each repo and still let you do shared configs across the org by defining your own plugin repos. - Better ignores: You can define line and project level ignores in the repo - Still have nightly reporting: We do let you run nightly on all changes and report them to track code base health and catch high-risk vulnerabilities and issues. There's a web app to view everything.

Try it and let me know how it goes. https://docs.trunk.io/check/usage