Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update context for US Gov #9510

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jason-dou
Copy link

Important

Required for API changes:

  • Link to API.md file: ADD LINK HERE
  • Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

Add other supporting information, such as a description of the PR changes:

Current description implies that all three environments in US Government context are in US Gov cloud. However, Microsoft 365 GCC environment is in Public cloud. Updating the description to avoid confusion.


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Copy link

Learn Build status updates of commit 032e3ef:

✅ Validation status: passed

File Status Preview URL Details
concepts/deployments.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@jason-dou jason-dou added the ready for content review PR is ready for a content review - content development and tech review are complete. label Feb 6, 2025
@Danielabom Danielabom self-assigned this Feb 11, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot removed the ready for content review PR is ready for a content review - content development and tech review are complete. label Feb 11, 2025
Copy link
Contributor

@Danielabom Danielabom left a comment

Choose a reason for hiding this comment

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

PR approved.

@Danielabom Danielabom added content review complete Apply when the content review is complete on a PR. and removed content review in progress labels Feb 11, 2025
@jason-dou jason-dou added the ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content review complete Apply when the content review is complete on a PR. ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants