docs: description updates (#408)

gr2m · web-flow · commit 07bb7ece7579 · 2021-06-27T12:40:20.000-07:00
diff --git a/docs/apps/createInstallationAccessToken.md b/docs/apps/createInstallationAccessToken.md
@@ -178,6 +178,11 @@ The level of permission to grant the access token for viewing an organization's
 
 The level of permission to grant the access token to manage organization projects, columns, and cards. Can be one of: `read`, `write`, or `admin`.
 
+</td></tr>
+<tr><td>permissions.organization_packages</td><td>no</td><td>
+
+The level of permission to grant the access token for organization packages published to GitHub Packages. Can be one of: `read` or `write`.
+
 </td></tr>
 <tr><td>permissions.organization_secrets</td><td>no</td><td>
 
diff --git a/docs/apps/scopeToken.md b/docs/apps/scopeToken.md
@@ -192,6 +192,11 @@ The level of permission to grant the access token for viewing an organization's
 
 The level of permission to grant the access token to manage organization projects, columns, and cards. Can be one of: `read`, `write`, or `admin`.
 
+</td></tr>
+<tr><td>permissions.organization_packages</td><td>no</td><td>
+
+The level of permission to grant the access token for organization packages published to GitHub Packages. Can be one of: `read` or `write`.
+
 </td></tr>
 <tr><td>permissions.organization_secrets</td><td>no</td><td>
 
diff --git a/docs/billing/getGithubPackagesBillingOrg.md b/docs/billing/getGithubPackagesBillingOrg.md
@@ -8,7 +8,7 @@ type: API method
 
 # Get GitHub Packages billing for an organization
 
-Gets the free and paid storage usued for GitHub Packages in gigabytes.
+Gets the free and paid storage used 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)."
 
diff --git a/docs/packages/deletePackageForAuthenticatedUser.md b/docs/packages/deletePackageForAuthenticatedUser.md
@@ -33,7 +33,7 @@ octokit.rest.packages.deletePackageForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/deletePackageForOrg.md b/docs/packages/deletePackageForOrg.md
@@ -36,7 +36,7 @@ octokit.rest.packages.deletePackageForOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/deletePackageVersionForAuthenticatedUser.md b/docs/packages/deletePackageVersionForAuthenticatedUser.md
@@ -34,7 +34,7 @@ octokit.rest.packages.deletePackageVersionForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/deletePackageVersionForOrg.md b/docs/packages/deletePackageVersionForOrg.md
@@ -37,7 +37,7 @@ octokit.rest.packages.deletePackageVersionForOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getAllPackageVersionsForAPackageOwnedByAnOrg.md b/docs/packages/getAllPackageVersionsForAPackageOwnedByAnOrg.md
@@ -36,7 +36,7 @@ octokit.rest.packages.getAllPackageVersionsForAPackageOwnedByAnOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getAllPackageVersionsForAPackageOwnedByTheAuthenticatedUser.md b/docs/packages/getAllPackageVersionsForAPackageOwnedByTheAuthenticatedUser.md
@@ -37,7 +37,7 @@ octokit.rest.packages.getAllPackageVersionsForAPackageOwnedByTheAuthenticatedUse
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getAllPackageVersionsForPackageOwnedByAuthenticatedUser.md b/docs/packages/getAllPackageVersionsForPackageOwnedByAuthenticatedUser.md
@@ -33,7 +33,7 @@ octokit.rest.packages.getAllPackageVersionsForPackageOwnedByAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getAllPackageVersionsForPackageOwnedByOrg.md b/docs/packages/getAllPackageVersionsForPackageOwnedByOrg.md
@@ -34,7 +34,7 @@ octokit.rest.packages.getAllPackageVersionsForPackageOwnedByOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getAllPackageVersionsForPackageOwnedByUser.md b/docs/packages/getAllPackageVersionsForPackageOwnedByUser.md
@@ -34,7 +34,7 @@ octokit.rest.packages.getAllPackageVersionsForPackageOwnedByUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageForAuthenticatedUser.md b/docs/packages/getPackageForAuthenticatedUser.md
@@ -33,7 +33,7 @@ octokit.rest.packages.getPackageForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageForOrganization.md b/docs/packages/getPackageForOrganization.md
@@ -34,7 +34,7 @@ octokit.rest.packages.getPackageForOrganization({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageForUser.md b/docs/packages/getPackageForUser.md
@@ -34,7 +34,7 @@ octokit.rest.packages.getPackageForUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageVersionForAuthenticatedUser.md b/docs/packages/getPackageVersionForAuthenticatedUser.md
@@ -34,7 +34,7 @@ octokit.rest.packages.getPackageVersionForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageVersionForOrganization.md b/docs/packages/getPackageVersionForOrganization.md
@@ -35,7 +35,7 @@ octokit.rest.packages.getPackageVersionForOrganization({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/getPackageVersionForUser.md b/docs/packages/getPackageVersionForUser.md
@@ -35,7 +35,7 @@ octokit.rest.packages.getPackageVersionForUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/restorePackageForAuthenticatedUser.md b/docs/packages/restorePackageForAuthenticatedUser.md
@@ -37,7 +37,7 @@ octokit.rest.packages.restorePackageForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/restorePackageForOrg.md b/docs/packages/restorePackageForOrg.md
@@ -41,7 +41,7 @@ octokit.rest.packages.restorePackageForOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/restorePackageVersionForAuthenticatedUser.md b/docs/packages/restorePackageVersionForAuthenticatedUser.md
@@ -38,7 +38,7 @@ octokit.rest.packages.restorePackageVersionForAuthenticatedUser({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/packages/restorePackageVersionForOrg.md b/docs/packages/restorePackageVersionForOrg.md
@@ -42,7 +42,7 @@ octokit.rest.packages.restorePackageVersionForOrg({
   <tbody>
     <tr><td>package_type</td><td>yes</td><td>
 
-The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. For Docker images that use the package namespace `https://ghcr.io/owner/package-name`, use `container`.
+The type of supported package. Can be one of `npm`, `maven`, `rubygems`, `nuget`, `docker`, or `container`. Packages in GitHub's Gradle registry have the type `maven`. Docker images pushed to GitHub's Container registry (`ghcr.io`) have the type `container`. You can use the type `docker` to find images that were pushed to GitHub's Docker registry (`docker.pkg.github.com`), even if these have now been migrated to the Container registry.
 
 </td></tr>
 <tr><td>package_name</td><td>yes</td><td>
diff --git a/docs/projects/moveCard.md b/docs/projects/moveCard.md
@@ -33,7 +33,7 @@ card_id parameter
 </td></tr>
 <tr><td>position</td><td>yes</td><td>
 
-The position of the card in a column
+The position of the card in a column. Can be one of: `top`, `bottom`, or `after:<card_id>` to place after the specified card.
 
 </td></tr>
 <tr><td>column_id</td><td>no</td><td>
diff --git a/docs/projects/moveColumn.md b/docs/projects/moveColumn.md
@@ -33,7 +33,7 @@ column_id parameter
 </td></tr>
 <tr><td>position</td><td>yes</td><td>
 
-The position of the column in a project
+The position of the column in a project. Can be one of: `first`, `last`, or `after:<column_id>` to place after the specified column.
 
 </td></tr>
   </tbody>
diff --git a/docs/repos/update.md b/docs/repos/update.md
@@ -59,6 +59,31 @@ Either `true` to make the repository private or `false` to make it public. Defau
 
 Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. The `visibility` parameter overrides the `private` parameter when you use both along with the `nebula-preview` preview header.
 
+</td></tr>
+<tr><td>security_and_analysis</td><td>no</td><td>
+
+Specify which security and analysis features to enable or disable. For example, to enable GitHub Advanced Security, use this data in the body of the PATCH request: `{"security_and_analysis": {"advanced_security": {"status": "enabled"}}}`. If you have admin permissions for a private repository covered by an Advanced Security license, you can check which security and analysis features are currently enabled by using a `GET /repos/{owner}/{repo}` request.
+
+</td></tr>
+<tr><td>security_and_analysis.advanced_security</td><td>no</td><td>
+
+Use the `status` property to enable or disable GitHub Advanced Security for this repository. For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/learning-about-github/about-github-advanced-security)."
+
+</td></tr>
+<tr><td>security_and_analysis.advanced_security.status</td><td>no</td><td>
+
+Can be `enabled` or `disabled`.
+
+</td></tr>
+<tr><td>security_and_analysis.secret_scanning</td><td>no</td><td>
+
+Use the `status` property to enable or disable secret scanning for this repository. For more information, see "[About secret scanning](/code-security/secret-security/about-secret-scanning)."
+
+</td></tr>
+<tr><td>security_and_analysis.secret_scanning.status</td><td>no</td><td>
+
+Can be `enabled` or `disabled`.
+
 </td></tr>
 <tr><td>has_issues</td><td>no</td><td>
 
diff --git a/docs/repos/updateBranchProtection.md b/docs/repos/updateBranchProtection.md
diff --git a/docs/search/labels.md b/docs/search/labels.md
diff --git a/docs/search/topics.md b/docs/search/topics.md
diff --git a/docs/secretScanning/listAlertsForRepo.md b/docs/secretScanning/listAlertsForRepo.md
diff --git a/docs/users/setPrimaryEmailVisibilityForAuthenticated.md b/docs/users/setPrimaryEmailVisibilityForAuthenticated.md
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
diff --git a/scripts/update-endpoints/fetch-json.js b/scripts/update-endpoints/fetch-json.js
diff --git a/scripts/update-endpoints/generated/endpoints.json b/scripts/update-endpoints/generated/endpoints.json
diff --git a/src/generated/method-types.ts b/src/generated/method-types.ts
