Skip to content

Add CodeQL workflow for code analysis - #162

Closed
testtest126 wants to merge 2 commits into
mainfrom
testtest126-patch-5
Closed

Add CodeQL workflow for code analysis#162
testtest126 wants to merge 2 commits into
mainfrom
testtest126-patch-5

Conversation

@testtest126

Copy link
Copy Markdown
Owner

Summary

Test plan

  • swift test in ChessKit/ passes
  • swift test in chess-server/ passes (if server code changed)
  • App builds / relevant UI tests pass (if app code changed)

@testtest126 testtest126 added the help wanted Extra attention is needed label Jul 14, 2026
@testtest126 testtest126 added this to the TestFlight 1.0 milestone Jul 14, 2026
This workflow's own jobs (Analyze (actions), Analyze (swift)) fail with:
"CodeQL analyses from advanced configurations cannot be processed when the
default setup is enabled" — confirmed via the failing check's annotations.

The repo already has GitHub's default-setup CodeQL code scanning enabled and
working (visible as the separate "CodeQL" check, green on every other PR).
Running a second, redundant advanced-configuration workflow for the same
languages doesn't add coverage, it just collides with the config already in
place. Disabling default setup instead was considered and rejected: it's a
repo Settings change (not expressible in this branch's diff), it would affect
every other branch/PR relying on it, and it's a larger, harder-to-reverse
change than removing one redundant file. Removing the added workflow is the
smaller, fully-reversible fix, and leaves exactly one working CodeQL path.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@testtest126

Copy link
Copy Markdown
Owner Author

Closing per owner decision — not adopting this scanner for now; reopen anytime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

help wanted Extra attention is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant