repo sync

Author: Octomerger

content/github/administering-a-repository/about-secret-scanning.md

@@ -20,7 +20,7 @@ Service providers can partner with {% data variables.product.company_short %} to
 
  {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)."
 
-When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. 
+When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets.
 
 When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider.
 
@@ -36,6 +36,7 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred
 - Databricks
 - Datadog
 - Discord
+- Doppler
 - Dropbox
 - Dynatrace
 - Finicity
@@ -90,6 +91,7 @@ Repository administrators and organization owners can grant users and team acces
 - CloudBees CodeShip
 - Databricks
 - Discord
+- Doppler
 - Dropbox
 - Dynatrace
 - Finicity

content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md

@@ -20,7 +20,7 @@ versions:
 
 ### 1. Back up your organization content
 
-Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, and issues from the account.
+Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
 
 ### 2. Delete the organization
 

lib/rest/static/decorated/api.github.com.json

@@ -41282,6 +41282,11 @@
         "httpStatusMessage": "Accepted",
         "description": "Response"
       },
+      {
+        "httpStatusCode": "400",
+        "httpStatusMessage": "Bad Request",
+        "description": "Response if the sarif field is invalid"
+      },
       {
         "httpStatusCode": "403",
         "httpStatusMessage": "Forbidden",
@@ -41291,6 +41296,11 @@
         "httpStatusCode": "404",
         "httpStatusMessage": "Not Found",
         "description": "Response if commit sha or ref cannot be found"
+      },
+      {
+        "httpStatusCode": "413",
+        "httpStatusMessage": "Payload Too Large",
+        "description": "Response if the sarif field is too large"
       }
     ],
     "descriptionHTML": "<p>Upload a SARIF file containing the results of a code scanning analysis to make the results available in a repository.\nFor private repos, you must use an access token with the <code>repo</code> scope. For public repos, you must use an access token with <code>public_repo</code> and <code>repo:security_events</code> scopes. GitHub Apps must have the <code>security_events</code> write permission to use this endpoint.</p>",

lib/rest/static/decorated/ghes-2.18.json

@@ -39166,6 +39166,11 @@
         "httpStatusMessage": "Accepted",
         "description": "Response"
       },
+      {
+        "httpStatusCode": "400",
+        "httpStatusMessage": "Bad Request",
+        "description": "Response if the sarif field is invalid"
+      },
       {
         "httpStatusCode": "403",
         "httpStatusMessage": "Forbidden",
@@ -39175,6 +39180,11 @@
         "httpStatusCode": "404",
         "httpStatusMessage": "Not Found",
         "description": "Response if commit sha or ref cannot be found"
+      },
+      {
+        "httpStatusCode": "413",
+        "httpStatusMessage": "Payload Too Large",
+        "description": "Response if the sarif field is too large"
       }
     ],
     "descriptionHTML": "<p>Upload a SARIF file containing the results of a code scanning analysis to make the results available in a repository.\nFor private repos, you must use an access token with the <code>repo</code> scope. For public repos, you must use an access token with <code>public_repo</code> and <code>repo:security_events</code> scopes. GitHub Apps must have the <code>security_events</code> write permission to use this endpoint.</p>",

lib/rest/static/decorated/ghes-2.19.json

@@ -125547,6 +125547,12 @@
           },
           "404": {
             "description": "Response if `commit_sha` or `ref` cannot be found"
+          },
+          "400": {
+            "description": "Response if the `sarif` field is invalid"
+          },
+          "413": {
+            "description": "Response if the `sarif` field is too large"
           }
         },
         "x-github": {