Add Missing Languages to CodeQL Advanced Configuration

[bkungl]

We are working to improve and streamline CodeQL configuration at GitHub. Your repository

1. Uses advanced CodeQL configuration
2. Has languages in the repository that are not configured to be scanned by Code Scanning (CodeQL)

This PR adds those languages to your configuration. Merging this PR will ensure code scanning happens in your repo reliably and should eliminate future findings in Security Findings (assuming you update the configuration as contents of your repository changes).

If your repository does not require or benefit from advanced config (e.g. for compiled languages), you can change to default setup in lieu of merging this PR.

If you have concerns or questions about this, please mention @github/prodsec-engineering in this PR or drop in our slack channel with your question.

If this configuration update will work for your repository, please approve and merge this pull request

[Copilot]

Pull Request Overview

This PR adds the "actions" language to the CodeQL Advanced Configuration to ensure comprehensive code scanning coverage. The change addresses a gap where GitHub Actions workflows in the repository were not being scanned by CodeQL.

• Adds "actions" language to the CodeQL language matrix for complete repository scanning coverage

[Copilot]

The 'actions' language is not listed in the CodeQL supported languages comment on line 25. Consider updating the comment to reflect that 'actions' is also supported, or verify that 'actions' is a valid CodeQL language as it's not mentioned in the existing documentation comment.

Suggested change

	language: [ actions, go, python ]
	language: [ go, python ]

[github-advanced-security]

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.

[github-service-catalog]

It looks like this PR might be missing Durable Ownership Scorecard check. Here is what to do:

• 🟠 Expected — Waiting for workflow to run (stuck) - Your PR probably predates the repository enrollment.
  • Please reopen the PR or push a new commit to trigger the check.
• ✅ Successful in XXs — Workflow passed - Your PR has a passing check:
  • Great! No further action is needed - this message can be ignored or deleted.

---

You can read more about this check on TheHub. If you have any questions, please reach out in #service-catalog