Removed whitespace in logging commands #20939
Open
Conversation
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
manolerazvan
approved these changes
Mar 24, 2025
|
@manolerazvan can you run the status checks? |
|
@v-gayatrij / @mmrazik as commentors on the previous incarnation of this PR, can you run the status checks? I'm unable to add labels to the PR to raise awareness in the particular groups. |
|
Updated sprint number. @manolerazvan can you reapprove, and kick off the CI tasks? |
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.
Task name: AzurePowerShell@v5, AzurePowerShell@v4
Description: Removed the spaces at the beginning of certain logging messages that don't conform to the convention:
Risk Assesment(Low/Medium/High): Low
Added unit tests: N
Tests Performed: Y
AzurePowerShellV4:
AzurePowerShellV5:
Documentation changes required: N
Attached related issue: N
Checklist: