Repository navigation
Scan Java with CodeQL advanced setup and a Gradle build [no-new-version] - #18
Merged
Merged
Conversation
The CodeQL default setup extracts this Java-only project with build-mode none, which cannot fetch the AndroidX AARs from Google Maven: RecyclerView stays unresolved and the analysis quality drops below the thresholds. Build it with Gradle (autobuild) as the default setup already does for MaterialSeekArc, which contains Kotlin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0178vjPYCurDqWnpvkLsVmZ1
Owner
Author
|
The analysis itself works (the Gradle build ends with Generated by Claude Code |
A push that keeps an already released version left the release commit status pending forever. A commit message with [no-new-version] now marks it as intentional and reports success. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0178vjPYCurDqWnpvkLsVmZ1
simonebortolin
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The CodeQL default setup scans this Java-only project with
build-mode: none. Buildless extraction tries to download the dependencies as.jarfiles, but the AndroidX libraries on Google Maven are AARs, so 13 fetches fail (androidx.recyclerview:recyclerview:jar:1.4.0, ...). RecyclerView stays unresolved and CodeQL reports Low Java analysis quality (calls with call target: 82 %, threshold 85 %).MaterialSeekArc does not have the problem because it contains Kotlin, so the default setup builds it with
autobuild.This PR adds
.github/workflows/codeql.yml(advanced setup):java-kotlinwithbuild-mode: autobuild(Gradle build on JDK 17, so the dependencies are resolved by Gradle)actionswithbuild-mode: none, as todaymaster, weekly, and manuallyIt also changes
ci.yml: a push tomasterthat keeps an already releasedVERSION_NAMEleft thereleasecommit status pending forever. When a pushed commit message contains[no-new-version], the Report release status step now reports success instead. This PR does not bump the version and carries the tag, so its merge already reports success.Disable the CodeQL default setup in Settings → Code security → CodeQL analysis. While it is enabled, GitHub rejects the results uploaded by an advanced workflow, so the
Analyzejobs of this PR fail until then.Testing
[no-new-version]detection checked in bash.Analyze (java-kotlin)job already builds with Gradle (BUILD SUCCESSFUL) without the low-quality diagnostics; only the upload is rejected while the default setup is enabled.🤖 Generated with Claude Code
https://claude.ai/code/session_0178vjPYCurDqWnpvkLsVmZ1