Add CodeQL advanced setup workflow to fix failing runs#1
Conversation
This commit adds a dedicated CodeQL workflow to the repository. It addresses the failing "Default Setup" runs by: 1. Limiting analysis to the `main` branch, avoiding failures on the `gh-pages` branch. 2. Replacing the fragile "autobuild" with manual Gradle build steps using JDK 17. 3. Explicitly setting up the environment to match the project's requirements. Co-authored-by: hick209 <927983+hick209@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This commit adds a dedicated CodeQL workflow to the repository. It addresses the failing "Default Setup" runs by: 1. Limiting analysis to the `main` branch, avoiding failures on the `gh-pages` branch. 2. Replacing the fragile "autobuild" with manual Gradle build steps using JDK 17. 3. Adding a weekly schedule trigger for periodic scanning. 4. Explicitly setting up the environment to match the project's requirements. Co-authored-by: hick209 <927983+hick209@users.noreply.github.com>
This commit adds a dedicated "CodeQL (Advanced Setup)" workflow. It fixes the failing built-in "Default Setup" runs by: 1. Limiting analysis to the `main` branch, avoiding failures on the `gh-pages` branch. 2. Replacing the fragile "autobuild" with manual Gradle build steps using JDK 17. 3. Adding a weekly schedule trigger for periodic scanning. Note: Once this is merged, the "Default Setup" for CodeQL should be disabled in the repository settings to remove the duplicate failing workflow. Co-authored-by: hick209 <927983+hick209@users.noreply.github.com>
1 participant
I have added an explicit CodeQL workflow file at
.github/workflows/codeql.yml. This fixes the issue where GitHub's default CodeQL analysis was failing on thegh-pagesbranch (which contains only build artifacts) and failing to build the Java/Kotlin code on themainbranch.The new workflow:
mainbranch pushes and pull requests.PR created automatically by Jules for task 11234153978370889056 started by @hick209