We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm automating running TLint using Duster with https://github.com/indykoning/grumphp-duster With small changes this task creates a lot of spam in the form of LGTM! messages
LGTM!
This is what it looks like with ~20 files Which blows up with more files, pushing any useful feedback away.
It would be really nice to have an option to configure where the positive output is silenced and only things that need to be fixed get outputted
The text was updated successfully, but these errors were encountered:
What does this LGTM! even mean? Im trying to lint a blade file and all I get is one LGTM error, thats it.
Sorry, something went wrong.
I'm updating Duster to prevent this output: tighten/duster#167
No branches or pull requests
I'm automating running TLint using Duster with https://github.com/indykoning/grumphp-duster
With small changes this task creates a lot of spam in the form of
LGTM!
messagesThis is what it looks like with ~20 files
Which blows up with more files, pushing any useful feedback away.
It would be really nice to have an option to configure where the positive output is silenced and only things that need to be fixed get outputted
The text was updated successfully, but these errors were encountered: