Skip to content

Update site-follow.md#9952

Open
rykoma wants to merge 1 commit into
microsoftgraph:mainfrom
rykoma:patch-44
Open

Update site-follow.md#9952
rykoma wants to merge 1 commit into
microsoftgraph:mainfrom
rykoma:patch-44

Conversation

@rykoma

@rykoma rykoma commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgo for more information.

Required for API changes:


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

Updated user ID in the follow site API request example, because it was not a valid GUID format.


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.

Updated user ID in the follow site API request example, because it was not a valid GUID format.
@rykoma rykoma added the ready for content review PR is ready for a content review - content development and tech review are complete. label Jun 25, 2026
@microsoft-github-policy-service

Copy link
Copy Markdown
Contributor

Thank you for indicating that your pull request is ready for content review, @@rykoma. It has been added to the Content Review project and an available reviewer will be assigned in the next one (1) business day, depending on demand. If this PR relates to any schema changes, refer to the pull request description box for quick instructions to move this PR forward.

Check the content review workflow here.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5199f43:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/site-follow.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for content review PR is ready for a content review - content development and tech review are complete.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant