Skip to content

Update engagementrole-post-members.md#9579

Merged
Danielabom merged 1 commit into
microsoftgraph:mainfrom
richafnu:patch-2
Jul 17, 2025
Merged

Update engagementrole-post-members.md#9579
Danielabom merged 1 commit into
microsoftgraph:mainfrom
richafnu:patch-2

Conversation

@richafnu
Copy link
Copy Markdown
Contributor

Updated Example call

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:

Update the request reader in the provided example


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.

@richafnu richafnu requested a review from Copilot May 29, 2025 20:17
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the example in engagementrole-post-members.md to align with recent API changes. The updated example now uses the "user@odata.bind" property to demonstrate binding a user resource.

  • Removed the explicit "@odata.type" and "userId" properties.
  • Introduced a URL binding for the user reference in the request payload.

Comment thread api-reference/beta/api/engagementrole-post-members.md
@richafnu richafnu added the ready for content review PR is ready for a content review - content development and tech review are complete. label May 29, 2025
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 4012111:

✅ Validation status: passed

File Status Preview URL Details
api-reference/beta/api/engagementrole-post-members.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@richafnu richafnu requested a review from Danielabom June 2, 2025 20:07
Copy link
Copy Markdown
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. ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. and removed ready for content review PR is ready for a content review - content development and tech review are complete. labels Jul 17, 2025
@Danielabom Danielabom merged commit d13c41e into microsoftgraph:main Jul 17, 2025
6 checks passed
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

Thank you for your work in this PR, @@richafnu.

When the updates in this PR are ready for external customers to use, please replace the do not merge label with ready to merge.

Check the content review workflow here.

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.

3 participants