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

Update backuprestoreroot-list-restorepoints.md #9436

Closed
wants to merge 4 commits into from

Conversation

tannikaM
Copy link
Contributor

@tannikaM tannikaM commented Oct 9, 2024

Changing the permissions to BackupRestore-Search.Read.All

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.

Changing the permissions to BackupRestore-Search.Read.All
Copy link

Learn Build status updates of commit 4d0f4b0:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
api-reference/beta/api/educationalactivity-delete.md ❌Error Details
api-reference/beta/api/educationalactivity-get.md ❌Error Details
api-reference/beta/api/educationalactivity-update.md ❌Error Details

api-reference/beta/api/educationalactivity-delete.md

  • Line 37, Column 1: [Error: include-not-found - See documentation] Invalid include link: '../includes/permissions/educationalactivity-delete-permissions.md'.

api-reference/beta/api/educationalactivity-get.md

  • Line 37, Column 1: [Error: include-not-found - See documentation] Invalid include link: '../includes/permissions/educationalactivity-get-permissions.md'.

api-reference/beta/api/educationalactivity-update.md

  • Line 37, Column 1: [Error: include-not-found - See documentation] Invalid include link: '../includes/permissions/educationalactivity-update-permissions.md'.

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:

@tannikaM
Copy link
Contributor Author

tannikaM commented Oct 9, 2024

Getting some errors in build from other branch. Can you please help.

@tannikaM tannikaM added the ready for content review PR is ready for a content review - content development and tech review are complete. label Oct 9, 2024
@Lauragra
Copy link
Contributor

@tannikaM , can you please follow up with me internally regarding this PR? We should make permissions updates via the JSON permissions model; its not clear to me why this topic has a manually authored table.

Copy link

Learn Build status updates of commit d2cbf6e:

✅ Validation status: passed

File Status Preview URL Details
api-reference/beta/includes/permissions/backuprestoreroot-list-restorepoints-permissions.md ✅Succeeded
api-reference/v1.0/api/backuprestoreroot-list-restorepoints.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit bbcccce:

✅ Validation status: passed

File Status Preview URL Details
api-reference/beta/api/backuprestoreroot-list-restorepoints.md ✅Succeeded
api-reference/beta/includes/permissions/backuprestoreroot-list-restorepoints-permissions.md ✅Succeeded
api-reference/v1.0/api/backuprestoreroot-list-restorepoints.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 91cebad:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
api-reference/v1.0/api/backuprestoreroot-list-restorepoints.md ❌Error Details

api-reference/v1.0/api/backuprestoreroot-list-restorepoints.md

  • Line 26, Column 1: [Error: include-not-found - See documentation] Invalid include link: '../includes/permissions/backuprestoreroot-list-restorepoints-permissions.md'.

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 closed this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting internal response 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.

3 participants