Skip to content

[AutoPublish] main to live - 06/10 14:16 PDT | 06/11 02:46 IST#1185

Merged
padmagit77 merged 2 commits into
livefrom
main
Jun 11, 2026
Merged

[AutoPublish] main to live - 06/10 14:16 PDT | 06/11 02:46 IST#1185
padmagit77 merged 2 commits into
livefrom
main

Conversation

@m365-skilling-repo-management

Copy link
Copy Markdown

@MicrosoftDocs/marveldocs-pubops

This is an automated pull request to publish changes from the main branch to the live branch. Merging this PR will publish the changes to the live learn.microsoft.com site.

Auto-merge is enabled. The repo will attempt to automatically merge this PR when all required checks pass. If the PR is automatically merged, no further action is required to publish the contents of this PR.

In the event the repo can't automatically merge this PR, the Manual merge required label will be added to the PR. If this happens, complete the following checks before merging this PR:

  • If there are more than 30 files, the repo will not automatically merge the PR. Review the changes for any obvious mistakes such as mass-deleted files. If the changes appear normal (bulk changes, general updates to many files, etc), merge the PR. If you're not sure, do not merge the PR and investigate further.
  • If there are warnings or failing checks, resolve them before merging the PR.
  • View the changes on https://review.learn.microsoft.com to confirm the changes look correct on the site.

After you've completed these steps, manually merge the PR.

If you have questions, post a message to https://aka.ms/tcphelp.

Co-authored-by: Gary Moore <5432776+garycentric@users.noreply.github.com>
@m365-skilling-repo-management m365-skilling-repo-management Bot requested a review from a team as a code owner June 10, 2026 21:16
@github-actions github-actions Bot added AutoPublish PR was automatically created for publishing from main to live. Sign off The pull request is ready to be reviewed and merged by PubOps Manual merge required An AutoPublish pull request requires a human to merge it. labels Jun 10, 2026
Updated the date for the Practitioners Calls Archive and added a new entry for the May 2026 call on the Frontier Firm maturity model.

Co-authored-by: Aditi Srivastava <133841950+aditisrivastava07@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 3d9f0e9:

✅ Validation status: passed

File Status Preview URL Details
Community/docfx.json ✅Succeeded
Community/practitioners-calls-archive.md ✅Succeeded View

For more details, please refer to the build report.

@github-actions

Copy link
Copy Markdown

@VesaJuvonen
You've been added as a reviewer to this pull request because you're listed as a Content Lead for the product area or feature covered by one or more articles in this PR.

Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:

  • The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
  • Article content has been checked for technical accuracy.
  • There are no errors or warnings in build validation.
  • There are no severity 1 or 2 PoliCheck issues.
  • All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

  1. Select the gear next to Labels.
  2. Select Sign off from the label list.
  3. Click away from the label list.

image

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to the submitter with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

@github-actions github-actions Bot requested a review from VesaJuvonen June 11, 2026 06:19
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@padmagit77 padmagit77 merged commit 28b5810 into live Jun 11, 2026
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoPublish PR was automatically created for publishing from main to live. Manual merge required An AutoPublish pull request requires a human to merge it. microsoft-365/svc Sign off The pull request is ready to be reviewed and merged by PubOps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants