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

Fixed change notification event types #9491

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

Conversation

AlessioCarminati
Copy link

Changed the event type property values based on the real event types that are returned in the payloads.

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:

ADD INFORMATION HERE


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.

Changed the event type property values based on the real event types that are returned in the payloads.
Copy link

Learn Build status updates of commit d62c06a:

✅ Validation status: passed

File Status Preview URL Details
concepts/changenotifications-for-onlinemeeting.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Danielabom
Copy link
Contributor

@AlessioCarminati, friendly reminder to please add the "ready for content review" label, if you're ready for a content reviewer to take your PR. Thanks!

@Danielabom Danielabom added the do not merge Use this label to indicate to the repository admins that your PR Is not ready to merge into master. label Jan 6, 2025
Copy link
Contributor

Hello @AlessioCarminati! This pull request has been inactive for 2 weeks with the do not merge label. Please update the pull request appropriately.

  • If you are still working on this pull request, please add a comment or push changes.
  • If the pull request is no longer needed, please close it.
  • If the pull request is ready for content review, please add the ready for content review label.
  • If the pull request is on hold or otherwise blocked, please add the blocked label.

Note

Pull requests that are inactive more than 6 weeks will be automatically closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge Use this label to indicate to the repository admins that your PR Is not ready to merge into master. inactive-2-weeks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants