feat: [Code Scanning] Security Improvements - create codeql.yml #1314
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.
Relates to:
[Enable CodeQL Analysis for Security Scanning] (#1313)
Risks
Low – The addition of CodeQL scanning is non-disruptive and will not affect existing application functionality. Minor risks include possible false positives or initial configuration errors, which can be addressed without impact to production workflows.
Background
What does this PR do?
This PR integrates CodeQL Analysis into the GitHub repository to enable automated security scanning of the codebase. CodeQL will analyze code for vulnerabilities, errors, and potential improvements across supported programming languages.
What kind of change is this?
Features – Non-breaking change that adds security functionality.
Why are we doing this?
To improve code security and quality by automating the detection of vulnerabilities and providing actionable insights directly within GitHub. This aligns with best practices for secure DevSecOps workflows.
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
Where should a reviewer start?
Detailed testing steps
Deploy Notes
No special deployment instructions are needed. The workflow is self-contained within the repository configuration.
Database changes
None.
Deployment instructions
Standard GitHub Action setup: merge the PR and ensure the workflow is triggered by future commits or pull requests.
This PR provides the foundation for continuous code security scanning using CodeQL and ensures our repository adheres to security best practices.