fix: enable giant-sentry-fist preview for octokit.orgs.blockUser / octokit.orgs.checkBlockedUser / octokit.orgs.listBlockedUsers / octokit.orgs.unblockUser / octokit.users.block / octokit.users.checkBlocked / octokit.users.listBlockedByAuthenticated / octokit.users.unblock (#313)

Author: octokitbot

docs/apps/suspendInstallation.md

@@ -12,8 +12,6 @@ type: API method
 
 Suspends a GitHub App on a user, organization, or business account, which blocks the app from accessing the account's resources. When a GitHub App is suspended, the app's access to the GitHub API or webhook events is blocked for that account.
 
-To suspend a GitHub App, you must be an account owner or have admin permissions in the repository or organization where the app is installed.
-
 You must use a [JWT](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint.
 
 ```js

docs/apps/unsuspendInstallation.md

@@ -12,8 +12,6 @@ type: API method
 
 Removes a GitHub App installation suspension.
 
-To unsuspend a GitHub App, you must be an account owner or have admin permissions in the repository or organization where the app is installed and suspended.
-
 You must use a [JWT](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint.
 
 ```js

docs/billing/getGithubActionsBillingOrg.md

@@ -12,7 +12,7 @@ Gets the summary of the free and paid GitHub Actions minutes used.
 
 Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see "[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)".
 
-Access tokens must have the `read:org` scope.
+Access tokens must have the `repo` or `admin:org` scope.
 
 ```js
 octokit.billing.getGithubActionsBillingOrg({

docs/billing/getGithubPackagesBillingOrg.md

@@ -12,7 +12,7 @@ Gets the free and paid storage usued for GitHub Packages in gigabytes.
 
 Paid minutes only apply to packages stored for private repositories. For more information, see "[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages)."
 
-Access tokens must have the `read:org` scope.
+Access tokens must have the `repo` or `admin:org` scope.
 
 ```js
 octokit.billing.getGithubPackagesBillingOrg({

docs/billing/getSharedStorageBillingOrg.md

@@ -12,7 +12,7 @@ Gets the estimated paid and estimated total storage used for GitHub Actions and
 
 Paid minutes only apply to packages stored for private repositories. For more information, see "[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages)."
 
-Access tokens must have the `read:org` scope.
+Access tokens must have the `repo` or `admin:org` scope.
 
 ```js
 octokit.billing.getSharedStorageBillingOrg({

docs/codeScanning/listAlertsForRepo.md

@@ -8,7 +8,7 @@ type: API method
 
 # List code scanning alerts for a repository
 
-Lists all open code scanning alerts for the default branch (usually `main` or `master`). For private repos, you must use an access token with the `repo` scope. For public repos, you must use an access token with `public_repo` and `repo:security_events` scopes. GitHub Apps must have the `security_events` read permission to use this endpoint.
+Lists all open code scanning alerts for the default branch (usually `main` or `master`). You must use an access token with the `security_events` scope to use this endpoint. GitHub Apps must have the `security_events` read permission to use this endpoint.
 
 ```js
 octokit.codeScanning.listAlertsForRepo({

docs/codeScanning/listRecentAnalyses.md

@@ -8,7 +8,7 @@ type: API method
 
 # List recent code scanning analyses for a repository
 
-List the details of recent code scanning analyses for a repository. For private repos, you must use an access token with the `repo` scope. For public repos, you must use an access token with `public_repo` and `repo:security_events` scopes. GitHub Apps must have the `security_events` read permission to use this endpoint.
+List the details of recent code scanning analyses for a repository. You must use an access token with the `security_events` scope to use this endpoint. GitHub Apps must have the `security_events` read permission to use this endpoint.
 
 ```js
 octokit.codeScanning.listRecentAnalyses({

docs/codeScanning/updateAlert.md

@@ -8,8 +8,7 @@ type: API method
 
 # Update a code scanning alert
 
-Updates the status of a single code scanning alert. For private repos, you must use an access token with the `repo` scope. For public repos, you must use an access token with `public_repo` and `repo:security_events` scopes.
-GitHub Apps must have the `security_events` write permission to use this endpoint.
+Updates the status of a single code scanning alert. You must use an access token with the `security_events` scope to use this endpoint. GitHub Apps must have the `security_events` write permission to use this endpoint.
 
 ```js
 octokit.codeScanning.updateAlert({

docs/codeScanning/uploadSarif.md

@@ -8,8 +8,7 @@ type: API method
 
 # Upload a SARIF file
 
-Upload a SARIF file containing the results of a code scanning analysis to make the results available in a repository.
-For private repos, you must use an access token with the `repo` scope. For public repos, you must use an access token with `public_repo` and `repo:security_events` scopes. GitHub Apps must have the `security_events` write permission to use this endpoint.
+Upload a SARIF file containing the results of a code scanning analysis to make the results available in a repository. You must use an access token with the `security_events` scope to use this endpoint. GitHub Apps must have the `security_events` write permission to use this endpoint.
 
 ```js
 octokit.codeScanning.uploadSarif({

docs/git/createTree.md

@@ -73,7 +73,8 @@ The content you want this file to have. GitHub will write this blob out and use
 </td></tr>
 <tr><td>base_tree</td><td>no</td><td>
 
-The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.
+The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.
+If not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.
 
 </td></tr>
   </tbody>

docs/pulls/createReviewComment.md

@@ -8,32 +8,14 @@ type: API method
 
 # Create a review comment for a pull request
 
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
 Creates a review comment in the pull request diff. To add a regular comment to a pull request timeline, see "[Create an issue comment](https://docs.github.com/rest/reference/issues#create-an-issue-comment)." We recommend creating a review comment using `line`, `side`, and optionally `start_line` and `start_side` if your comment applies to more than one line in the pull request diff.
 
-You can still create a review comment using the `position` parameter. When you use `position`, the `line`, `side`, `start_line`, and `start_side` parameters are not required. For more information, see [Multi-line comment summary](https://docs.github.com/rest/reference/pulls#multi-line-comment-summary-3).
+You can still create a review comment using the `position` parameter. When you use `position`, the `line`, `side`, `start_line`, and `start_side` parameters are not required. For more information, see the [`comfort-fade` preview notice](https://docs.github.com/rest/reference/pulls#create-a-review-comment-for-a-pull-request-preview-notices).
 
 **Note:** The position value equals the number of lines down from the first "@@" hunk header in the file you want to add a comment. The line just below the "@@" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.
 
 This endpoint triggers [notifications](https://help.github.com/articles/about-notifications/). Creating content too quickly using this endpoint may result in abuse rate limiting. See "[Abuse rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#abuse-rate-limits)" and "[Dealing with abuse rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)" for details.
 
-**Multi-line comment summary**
-
-**Note:** New parameters and response fields are available for developers to preview. During the preview period, these response fields may change without advance notice. Please see the [blog post](https://developer.github.com/changes/2019-10-03-multi-line-comments) for full details.
-
-Use the `comfort-fade` preview header and the `line` parameter to show multi-line comment-supported fields in the response.
-
-If you use the `comfort-fade` preview header, your response will show:
-
-- For multi-line comments, values for `start_line`, `original_start_line`, `start_side`, `line`, `original_line`, and `side`.
-- For single-line comments, values for `line`, `original_line`, and `side` and a `null` value for `start_line`, `original_start_line`, and `start_side`.
-
-If you don't use the `comfort-fade` preview header, multi-line and single-line comments will appear the same way in the response with a single `position` attribute. Your response will show:
-
-- For multi-line comments, the last line of the comment range for the `position` attribute.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. For more information, see `position` in the [input parameters](https://docs.github.com/rest/reference/pulls#parameters-2) table.
-
 ```js
 octokit.pulls.createReviewComment({
   owner,

docs/pulls/getReviewComment.md

@@ -8,28 +8,8 @@ type: API method
 
 # Get a review comment for a pull request
 
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
 Provides details for a review comment.
 
-**Multi-line comment summary**
-
-**Note:** New parameters and response fields are available for developers to preview. During the preview period, these response fields may change without advance notice. Please see the [blog post](https://developer.github.com/changes/2019-10-03-multi-line-comments) for full details.
-
-Use the `comfort-fade` preview header and the `line` parameter to show multi-line comment-supported fields in the response.
-
-If you use the `comfort-fade` preview header, your response will show:
-
-- For multi-line comments, values for `start_line`, `original_start_line`, `start_side`, `line`, `original_line`, and `side`.
-- For single-line comments, values for `line`, `original_line`, and `side` and a `null` value for `start_line`, `original_start_line`, and `start_side`.
-
-If you don't use the `comfort-fade` preview header, multi-line and single-line comments will appear the same way in the response with a single `position` attribute. Your response will show:
-
-- For multi-line comments, the last line of the comment range for the `position` attribute.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. For more information, see `position` in the [input parameters](https://docs.github.com/rest/reference/pulls#parameters-2) table.
-
-The `reactions` key will have the following payload where `url` can be used to construct the API location for [listing and creating](https://docs.github.com/rest/reference/reactions) reactions.
-
 ```js
 octokit.pulls.getReviewComment({
   owner,

docs/pulls/listReviewComments.md

@@ -8,28 +8,8 @@ type: API method
 
 # List review comments on a pull request
 
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
 Lists all review comments for a pull request. By default, review comments are in ascending order by ID.
 
-**Multi-line comment summary**
-
-**Note:** New parameters and response fields are available for developers to preview. During the preview period, these response fields may change without advance notice. Please see the [blog post](https://developer.github.com/changes/2019-10-03-multi-line-comments) for full details.
-
-Use the `comfort-fade` preview header and the `line` parameter to show multi-line comment-supported fields in the response.
-
-If you use the `comfort-fade` preview header, your response will show:
-
-- For multi-line comments, values for `start_line`, `original_start_line`, `start_side`, `line`, `original_line`, and `side`.
-- For single-line comments, values for `line`, `original_line`, and `side` and a `null` value for `start_line`, `original_start_line`, and `start_side`.
-
-If you don't use the `comfort-fade` preview header, multi-line and single-line comments will appear the same way in the response with a single `position` attribute. Your response will show:
-
-- For multi-line comments, the last line of the comment range for the `position` attribute.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. For more information, see `position` in the [input parameters](https://docs.github.com/rest/reference/pulls#parameters-2) table.
-
-The `reactions` key will have the following payload where `url` can be used to construct the API location for [listing and creating](https://docs.github.com/rest/reference/reactions) reactions.
-
 ```js
 octokit.pulls.listReviewComments({
   owner,

docs/pulls/listReviewCommentsForRepo.md

@@ -8,28 +8,8 @@ type: API method
 
 # List review comments in a repository
 
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
 Lists review comments for all pull requests in a repository. By default, review comments are in ascending order by ID.
 
-**Multi-line comment summary**
-
-**Note:** New parameters and response fields are available for developers to preview. During the preview period, these response fields may change without advance notice. Please see the [blog post](https://developer.github.com/changes/2019-10-03-multi-line-comments) for full details.
-
-Use the `comfort-fade` preview header and the `line` parameter to show multi-line comment-supported fields in the response.
-
-If you use the `comfort-fade` preview header, your response will show:
-
-- For multi-line comments, values for `start_line`, `original_start_line`, `start_side`, `line`, `original_line`, and `side`.
-- For single-line comments, values for `line`, `original_line`, and `side` and a `null` value for `start_line`, `original_start_line`, and `start_side`.
-
-If you don't use the `comfort-fade` preview header, multi-line and single-line comments will appear the same way in the response with a single `position` attribute. Your response will show:
-
-- For multi-line comments, the last line of the comment range for the `position` attribute.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. For more information, see `position` in the [input parameters](https://docs.github.com/rest/reference/pulls#parameters-2) table.
-
-The `reactions` key will have the following payload where `url` can be used to construct the API location for [listing and creating](https://docs.github.com/rest/reference/reactions) reactions.
-
 ```js
 octokit.pulls.listReviewCommentsForRepo({
   owner,

docs/pulls/updateReviewComment.md

@@ -8,26 +8,8 @@ type: API method
 
 # Update a review comment for a pull request
 
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
 Enables you to edit a review comment.
 
-**Multi-line comment summary**
-
-**Note:** New parameters and response fields are available for developers to preview. During the preview period, these response fields may change without advance notice. Please see the [blog post](https://developer.github.com/changes/2019-10-03-multi-line-comments) for full details.
-
-Use the `comfort-fade` preview header and the `line` parameter to show multi-line comment-supported fields in the response.
-
-If you use the `comfort-fade` preview header, your response will show:
-
-- For multi-line comments, values for `start_line`, `original_start_line`, `start_side`, `line`, `original_line`, and `side`.
-- For single-line comments, values for `line`, `original_line`, and `side` and a `null` value for `start_line`, `original_start_line`, and `start_side`.
-
-If you don't use the `comfort-fade` preview header, multi-line and single-line comments will appear the same way in the response with a single `position` attribute. Your response will show:
-
-- For multi-line comments, the last line of the comment range for the `position` attribute.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. For more information, see `position` in the [input parameters](https://docs.github.com/rest/reference/pulls#parameters-2) table.
-
 ```js
 octokit.pulls.updateReviewComment({
   owner,

docs/repos/getContent.md

@@ -9,7 +9,7 @@ type: API method
 # Get repository content
 
 Gets the contents of a file or directory in a repository. Specify the file path or directory in `:path`. If you omit
-`:path`, you will receive the contents of all files in the repository.
+`:path`, you will receive the contents of the repository's root directory. See the description below regarding what the API response includes for directories.
 
 Files and symlinks support [a custom media type](https://docs.github.com/rest/reference/repos#custom-media-types) for
 retrieving the raw content or rendered HTML (when supported). All content types support [a custom media

docs/users/checkBlocked.md

@@ -8,10 +8,6 @@ type: API method
 
 # Check if a user is blocked by the authenticated user
 
-If the user is blocked:
-
-If the user is not blocked:
-
 ```js
 octokit.users.checkBlocked({
   username,