Skip to content

Structure warning references in range [C4701, C4750] #5730

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Sep 4, 2025
Merged

Structure warning references in range [C4701, C4750] #5730

merged 5 commits into from
Sep 4, 2025

Conversation

Rageking8
Copy link
Contributor

This is batch 84 that structures error/warning references. See #5465 for more information.

@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit 8e31443:

✅ Validation status: passed

File Status Preview URL Details
docs/error-messages/compiler-warnings/compiler-warning-c4746.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4711.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4715.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4716.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4717.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4722.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4727.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4729.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4730.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4731.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4733.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4739.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4742.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4743.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4744.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4747.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4750.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-3-c4723.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-3-c4724.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-3-c4738.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-4-c4701.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-4-c4702.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-4-c4703.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-4-c4706.md ✅Succeeded
docs/error-messages/compiler-warnings/compiler-warning-level-4-c4709.md ✅Succeeded

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.

@prmerger-automator PRMerger Automator
Copy link
Contributor

PRMerger Results

Issue Description
Changed Files This PR contains more than 10 changed files.
File Change Percent This PR contains file(s) with more than 30% file change.

@v-dirichards
Copy link
Contributor

v-dirichards commented Sep 2, 2025 •
edited
Loading

@TylerMSFT

Can you review the proposed changes?

Editorial changes LGTM

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Sep 2, 2025
@Rageking8
Copy link
Contributor Author

@TylerMSFT

Can you review the proposed changes? Changes look good to merge.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

Just checking if you meant to include "Changes look good to merge."?

@v-dirichards
Copy link
Contributor

@TylerMSFT
Can you review the proposed changes? Changes look good to merge.
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

Just checking if you meant to include "Changes look good to merge."?

Yes, we're helping Tyler with some basic document formatting review, so it's a note for him that we've reviewed the basic formatting in the document. Tyler will still be giving it a technical review and the final sign off.

TylerMSFT
TylerMSFT approved these changes Sep 3, 2025
View reviewed changes
Copy link
Collaborator

@TylerMSFT TylerMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#sign-off. Thank you!

@prmerger-automator PRMerger Automator
Copy link
Contributor

@TylerMSFT, you can only sign off in the main PR conversation, not in review comments.

@TylerMSFT
Copy link
Collaborator

#sign-off

@prmerger-automator PRMerger Automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @

@v-dirichards v-dirichards merged commit 2c1517e into MicrosoftDocs:main Sep 4, 2025
2 checks passed
@Rageking8 Rageking8 deleted the structure-warning-references-in-range-c4701-c4750 branch September 4, 2025 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TylerMSFT TylerMSFT TylerMSFT approved these changes

Assignees

@TylerMSFT TylerMSFT

Labels
aq-pr-triaged Tracking label for the PR review team do-not-merge needs-human-review review-team-triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Rageking8 @v-dirichards @TylerMSFT