Fix typo in the alert message of InvalidatedEnvStringPointers.qll#943
Merged
jeongsoolee09 merged 1 commit intogithub:mainfrom Aug 18, 2025
Merged
Fix typo in the alert message of InvalidatedEnvStringPointers.qll#943jeongsoolee09 merged 1 commit intogithub:mainfrom
InvalidatedEnvStringPointers.qll#943jeongsoolee09 merged 1 commit intogithub:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes spelling errors in the InvalidatedEnvStringPointers.qll file and updates corresponding test expectations. The main change corrects "susequent" to "subsequent" in alert messages and "afer" to "after" in a code comment.
- Fixed spelling of "subsequent" in alert message
- Fixed spelling of "after" in code comment
- Updated test expected outputs to reflect the corrected spelling
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
cpp/common/src/codingstandards/cpp/rules/invalidatedenvstringpointers/InvalidatedEnvStringPointers.qll |
Fixed spelling errors in alert message and code comment |
cpp/common/test/rules/invalidatedenvstringpointers/InvalidatedEnvStringPointers.expected |
Updated expected test outputs with corrected spelling |
c/common/test/rules/invalidatedenvstringpointers/InvalidatedEnvStringPointers.expected |
Updated expected test outputs with corrected spelling |
change_notes/2025-08-15-typo-in-alert-message.md |
Added change note documenting the spelling fix |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixed the spelling of "subsequent" in the alert message of
InvalidatedEnvStringPointers.qll. Also fix the spelling of "after" in a code comment.Change request type
.ql,.qll,.qlsor unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.