version 1.1.12 for PhpStorm 2025.3 #70
Conversation
Danil42Russia
force-pushed
the
danil42russia/update_for_2025.3
branch
from
39f92cc to
e847822
Compare
gradle/libs.versions.toml
Outdated
| intelliJPlatform = { id = "org.jetbrains.intellij.platform", version.ref = "intelliJPlatform" } | ||
| kotlin = { id = "org.jetbrains.kotlin.jvm", version.ref = "kotlin" } | ||
| kover = { id = "org.jetbrains.kotlinx.kover", version.ref = "kover" } | ||
| qodana = { id = "org.jetbrains.qodana", version.ref = "qodana" } |
There was a problem hiding this comment.
It seems it isn't necessary to add qodana as a gradle plugin because in the CI qodana from its docker image is being used
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2025.1.1
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
No description provided.