Skip to content

Frist draft to update meeting artifacts #9465

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

Merged
merged 6 commits into from
Nov 23, 2024
Merged

Frist draft to update meeting artifacts #9465

merged 6 commits into from
Nov 23, 2024

Conversation

garchiro7
Copy link
Contributor

The content is outdated and confused security reviewers from Eli Lilly and destroys trust with Microsoft.


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.

Copy link

Learn Build status updates of commit a8620c6:

⚠️ Validation status: warnings

File Status Preview URL Details
concepts/cloud-communications-online-meeting-artifacts.md ⚠️Warning Details

concepts/cloud-communications-online-meeting-artifacts.md

  • Line 13, Column 1: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
  • Line 28, Column 53: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.

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:

Copy link

Learn Build status updates of commit f5120f4:

⚠️ Validation status: warnings

File Status Preview URL Details
concepts/cloud-communications-online-meeting-artifacts.md ⚠️Warning Details

concepts/cloud-communications-online-meeting-artifacts.md

  • Line 12, Column 89: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
  • Line 27, Column 53: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.

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:

Copy link

Learn Build status updates of commit 1f5ec7f:

⚠️ Validation status: warnings

File Status Preview URL Details
concepts/cloud-communications-online-meeting-artifacts.md ⚠️Warning Details

concepts/cloud-communications-online-meeting-artifacts.md

  • Line 12, Column 123: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
  • Line 27, Column 53: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.

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:

@garchiro7
Copy link
Contributor Author

#sign-off

@microsoft-github-policy-service microsoft-github-policy-service bot added the ready for content review PR is ready for a content review - content development and tech review are complete. label Nov 21, 2024
@Lauragra Lauragra added 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 Nov 22, 2024
Copy link

Learn Build status updates of commit a1f325a:

⚠️ Validation status: warnings

File Status Preview URL Details
concepts/cloud-communications-online-meeting-artifacts.md ⚠️Warning Details

concepts/cloud-communications-online-meeting-artifacts.md

  • Line 12, Column 120: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
  • Line 26, Column 62: [Warning: link-out-of-scope - See documentation] File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.

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:

Copy link

Learn Build status updates of commit 834d4ec:

💡 Validation status: suggestions

File Status Preview URL Details
concepts/cloud-communications-online-meeting-artifacts.md 💡Suggestion Details

concepts/cloud-communications-online-meeting-artifacts.md

  • Line 26, Column 62: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/meetingattendancereport-get?view=graph-rest-1.0&tabs=http#permissions

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 Lauragra self-assigned this Nov 22, 2024
@Lauragra Lauragra merged commit 5dde212 into microsoftgraph:main Nov 23, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

2 participants