- Notifications
You must be signed in to change notification settings - Fork8.1k
[release/v7.4] Add CodeQL suppressions for PowerShell intended behavior#25376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[release/v7.4] Add CodeQL suppressions for PowerShell intended behavior#25376
Uh oh!
There was an error while loading.Please reload this page.
Conversation
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
| Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
| Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
ee53c67 intoPowerShell:release/v7.4Uh oh!
There was an error while loading.Please reload this page.
microsoft-github-policy-servicebot commentedMay 2, 2025 • edited by unfurl-linksbot
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by unfurl-linksbot
Uh oh!
There was an error while loading.Please reload this page.
📣 Hey @@pwshBot, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗https://aka.ms/PSRepoFeedback |
Uh oh!
There was an error while loading.Please reload this page.
Backport of#25359 to release/v7.4
Triggered by@TravisEz13 on behalf of@anamnavi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
Choose either tooling or Customer impact.
Tooling Impact
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]