Skip to content

Update engagementrole-post-members.md #9579

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

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

Conversation

richafnu
Copy link
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
Contributor

@Copilot 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 "[email protected]" 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.

@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
Copy link
Contributor

Thank you for indicating that your pull request is ready for content review, @@richafnu. It has been added to the Content Review project and an available reviewer will be assigned in the next 15 business days, depending on demand.

Check the content review workflow here.

Copy link

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
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