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

POST call join with token document updating #9445

Conversation

v-shazilms
Copy link
Contributor

Instructions: Add any supporting information, such as a description of the PR changes, here.


Note

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. Your PR won't be reviewed until you add this label.
  • 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 5f470f0:

⚠️ Validation status: warnings

File Status Preview URL Details
api-reference/beta/api/application-post-calls.md ⚠️Warning Details
api-reference/v1.0/api/application-post-calls.md ⚠️Warning Details

api-reference/beta/api/application-post-calls.md

  • Line 2877, Column 1: [Warning: invalid-tab-group - See documentation] Tab group with different tab id set.

api-reference/v1.0/api/application-post-calls.md

  • Line 2318, Column 1: [Warning: invalid-tab-group - See documentation] Tab group with different tab id set.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@Lauragra
Copy link
Contributor

@v-shazilms , please open this PR in the private authoring repo. This is the public mirror for external contributions. Please see the Get started steps for information about how to contribute: https://dev.azure.com/msazure/One/_wiki/wikis/Microsoft%20Graph%20Partners/707657/Get-started

@Lauragra Lauragra closed this Oct 25, 2024
@v-shazilms v-shazilms deleted the v-shazilms/PostCallForJoinTokenCase branch October 25, 2024 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants