Skip to content

ci(codeql): rename advanced workflow for clearer actions history#33

Merged
GazaliAhmad merged 1 commit into
mainfrom
release/0.9.0
Jun 2, 2026
Merged

ci(codeql): rename advanced workflow for clearer actions history#33
GazaliAhmad merged 1 commit into
mainfrom
release/0.9.0

Conversation

@GazaliAhmad

Copy link
Copy Markdown
Owner

Summary

Rename the repo-owned advanced CodeQL workflow so it is visually distinct from the historical/default CodeQL entry in GitHub Actions.

Why

This change belongs now because the default-to-advanced CodeQL transition left two similarly named workflow entries in Actions, which made it harder to tell which one is the active repo-owned workflow.

  • it addresses workflow-name ambiguity during and after the CodeQL setup migration
  • it is a small CI follow-up to the recent advanced CodeQL switch, not a runtime or release milestone change

Included

  • rename the repo-owned workflow from CodeQL to CodeQL Advanced
  • keep the workflow file path and behavior unchanged

Not Included

Call out anything intentionally left out so the PR does not read larger than it is.

  • no trigger/path logic changes
  • no changes to runtime, docs, website, or release posture
  • no changes to GitHub security settings

Verification

List the exact checks or commands you ran.

Get-Content .github/workflows/codeql.yml

If this is perf, runtime-stability, or website work, include the specific profile, route, or build command used.

  • verified the workflow display-name change in .github/workflows/codeql.yml

Docs

Mark what was updated if the public behavior, release posture, or surfaced site changed.

  • README
  • CHANGELOG
  • ROADMAP
  • MAINTENANCE
  • RELEASE_PROCESS
  • COMPATIBILITY
  • guides
  • website
  • no docs change needed

Checklist

  • scope stays focused
  • verification matches the change
  • docs and release wording are aligned when needed
  • no unrelated changes were bundled in casually

@GazaliAhmad GazaliAhmad merged commit 33c8c09 into main Jun 2, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant