linters

It would be great to have a lint rule to flag when true or false is passed to a function.

As a solution the problem of a vague true/false value passed to a function, the "boolean trap", I have a habit of creating a self-documenting constant and using that instead.

Instead of redraw(true), I'll define const INLINE = true; and then use redraw(INLINE);.

Thanks for considering this

It would be great to not just have comments in pull request, but also github summary report for users, which are working on some branch but don't use pull requests. As bonus it's easier to navigate inside summary to artifacts, rather than by clicking in element of table in pull request message, than going to another page => artifacts -> scroll down -> find yours artifact. This workflow happened to

linear.app is a modern, pretty cool issue tracker which shouldn't be too difficult to integrate with. Pretty good first issue.

I didn't find how to pass PassedFiles as inline parameters in the README, so went to source code and found this function. It would be great to add handling between the loader from the config and the output of the git ls-files. Unfortunately, I don't write program

It will be great to have a docker image that one can run locally or in CI instead of needing to install/download a binary.

	// makeExample replaces all ${linter} placeholders to a bound linter name.

The code below does not use ${linter} anywhere.
I could remove this, but would also like to avoid doing several unrelated things on the same PR, so keeping it as an issue to avoid forgetting about it.