do you run `detekt` on debug or release build type and why?

# android

[arekolek]

do you run detekt on debug or release build type and why?

[arekolek]

I see this in samples:

// Android: Don't create tasks for the specified build types (e.g. "release")
    ignoredBuildTypes = ["release"]

    // Android: Don't create tasks for the specified build flavor (e.g. "production")
    ignoredFlavors = ["production"]

    // Android: Don't create tasks for the specified build variants (e.g. "productionRelease")
    ignoredVariants = ["productionRelease"]

which seems like normally you would run it on debug, but it seems to me you want to check the release especially

[Zun]

Why would you care about code analysis in release builds? The tool is there to assist you during development. "Detekt helps you write cleaner Kotlin code so you can focus on what matters the most building amazing software."

[Zach]

Run it for every PR. ktlint too

[arekolek]

Why would you care about code analysis in release builds?

not during release builds
but because you can have some sources under src/debug/java which you probably should care less about than about sources under src/release/java