Skip to content

Revise request and response sections in API docs#9785

Merged
Danipocket merged 3 commits intomicrosoftgraph:mainfrom
rykoma:patch-9
Feb 5, 2026
Merged

Revise request and response sections in API docs#9785
Danipocket merged 3 commits intomicrosoftgraph:mainfrom
rykoma:patch-9

Conversation

@rykoma
Copy link
Contributor

@rykoma rykoma commented Jan 29, 2026

Updated request and response sections in the drive item content format documentation.

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.

Updated request and response sections in the drive item content format documentation.
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit ba909fe:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/driveitem-get-content-format.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

@Danipocket Danipocket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR approved.

@Danipocket Danipocket self-assigned this Feb 5, 2026
@Danipocket Danipocket added the content review complete Apply when the content review is complete on a PR. label Feb 5, 2026
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit bb68e0e:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/driveitem-get-content-format.md ✅Succeeded

For more details, please refer to the build report.

@Danipocket Danipocket enabled auto-merge February 5, 2026 18:52
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit cf7ead6:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/driveitem-get-content-format.md ✅Succeeded

For more details, please refer to the build report.

@Danipocket Danipocket merged commit 64ec623 into microsoftgraph:main Feb 5, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content review complete Apply when the content review is complete on a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments