Vladimir Sitnikov

> As said above, I wonder what the signal/noise ratio would be given the line endings potential problem and the fact it is intended that people modify it if they...

The following should cover all the cases: ```yaml paths: - **/gradle-wrapper.jar ``` What I mean is even though GitHub Actions is free, it is not very wise to use that...

What's the point in homoglyphs?

>Here's a demo/example of a homoglyph attack update PR. >https://github.com/JLLeitschuh/playframework/pull/1/files Is `**/gradle-wrapper.jar` impacted there? If it is impacted, then Actions will be triggered. If the file is not impacted, then...

However, `gradlew` and `gradlew.bat` might indeed be complicated :-/

Just in case: what I mean by `gradlew.bat might indeed be complicated` is that `gradlew` itself might be spelled with weird characters. It would be hard to notice in case...

> The general assumption that we make about gradlew and gradle.bat files are that since they are human-readable Well. `gradlew` (with cyrrilic а) It might call `grade-wraper.jar` Have you noticed...

Just in case, the way to use `gradle-cache-action` would as follows, however, I'm not sure it needs to be added to `actions/cache` examples. ```yaml - uses: burrunan/gradle-cache-action@v1 name: Build with:...

I wonder if this issue has been resolved with Dokka 1.4+, see https://github.com/Kotlin/dokka/issues/157#issuecomment-684411489

It turns out that Dokka uses is `cross-project` configuration which is a no-no: https://github.com/Kotlin/dokka/blob/f2adc0a50462a63f7e1901db2e58077001acd622/runners/gradle-plugin/src/main/kotlin/org/jetbrains/dokka/gradle/AbstractDokkaParentTask.kt#L15-L17 The suggested approach is as follows: 1) Every "child" project declares its outputs. For instance, it...