docs/campaigns/createCampaign.md

@@ -0,0 +1,101 @@
+---
+name: Create a campaign for an organization
+example: octokit.rest.campaigns.createCampaign({ org, name, description, ends_at, code_scanning_alerts, code_scanning_alerts[].repository_id, code_scanning_alerts[].alert_numbers })
+route: POST /orgs/{org}/campaigns
+scope: campaigns
+type: API method
+---
+
+# Create a campaign for an organization
+
+Create a campaign for an organization.
+
+The authenticated user must be an owner or security manager for the organization to use this endpoint.
+
+OAuth app tokens and personal access tokens (classic) need the `security_events` scope to use this endpoint.
+
+Fine-grained tokens must have the "Code scanning alerts" repository permissions (read) on all repositories included
+in the campaign.
+
+```js
+octokit.rest.campaigns.createCampaign({
+        org,
+name,
+description,
+ends_at,
+code_scanning_alerts,
+code_scanning_alerts[].repository_id,
+code_scanning_alerts[].alert_numbers
+      })
+```
+
+## Parameters
+
+<table>
+  <thead>
+    <tr>
+      <th>name</th>
+      <th>required</th>
+      <th>description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>org</td><td>yes</td><td>
+
+The organization name. The name is not case sensitive.
+
+</td></tr>
+<tr><td>name</td><td>yes</td><td>
+
+The name of the campaign
+
+</td></tr>
+<tr><td>description</td><td>yes</td><td>
+
+A description for the campaign
+
+</td></tr>
+<tr><td>managers</td><td>no</td><td>
+
+The logins of the users to set as the campaign managers. At this time, only a single manager can be supplied.
+
+</td></tr>
+<tr><td>team_managers</td><td>no</td><td>
+
+The slugs of the teams to set as the campaign managers.
+
+</td></tr>
+<tr><td>ends_at</td><td>yes</td><td>
+
+The end date and time of the campaign. The date must be in the future.
+
+</td></tr>
+<tr><td>contact_link</td><td>no</td><td>
+
+The contact link of the campaign. Must be a URI.
+
+</td></tr>
+<tr><td>code_scanning_alerts</td><td>yes</td><td>
+
+The code scanning alerts to include in this campaign
+
+</td></tr>
+<tr><td>code_scanning_alerts[].repository_id</td><td>yes</td><td>
+
+The repository id
+
+</td></tr>
+<tr><td>code_scanning_alerts[].alert_numbers</td><td>yes</td><td>
+
+The alert numbers
+
+</td></tr>
+<tr><td>generate_issues</td><td>no</td><td>
+
+If true, will automatically generate issues for the campaign. The default is false.
+
+</td></tr>
+  </tbody>
+</table>
+
+See also: [GitHub Developer Guide documentation](https://docs.github.com/rest/campaigns/campaigns#create-a-campaign-for-an-organization).

docs/campaigns/deleteCampaign.md

@@ -0,0 +1,48 @@
+---
+name: Delete a campaign for an organization
+example: octokit.rest.campaigns.deleteCampaign({ org, campaign_number })
+route: DELETE /orgs/{org}/campaigns/{campaign_number}
+scope: campaigns
+type: API method
+---
+
+# Delete a campaign for an organization
+
+Deletes a campaign in an organization.
+
+The authenticated user must be an owner or security manager for the organization to use this endpoint.
+
+OAuth app tokens and personal access tokens (classic) need the `security_events` scope to use this endpoint.
+
+```js
+octokit.rest.campaigns.deleteCampaign({
+  org,
+  campaign_number,
+});
+```
+
+## Parameters
+
+<table>
+  <thead>
+    <tr>
+      <th>name</th>
+      <th>required</th>
+      <th>description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>org</td><td>yes</td><td>
+
+The organization name. The name is not case sensitive.
+
+</td></tr>
+<tr><td>campaign_number</td><td>yes</td><td>
+
+The campaign number.
+
+</td></tr>
+  </tbody>
+</table>
+
+See also: [GitHub Developer Guide documentation](https://docs.github.com/rest/campaigns/campaigns#delete-a-campaign-for-an-organization).

docs/campaigns/getCampaignSummary.md

@@ -0,0 +1,48 @@
+---
+name: Get a campaign for an organization
+example: octokit.rest.campaigns.getCampaignSummary({ org, campaign_number })
+route: GET /orgs/{org}/campaigns/{campaign_number}
+scope: campaigns
+type: API method
+---
+
+# Get a campaign for an organization
+
+Gets a campaign for an organization.
+
+The authenticated user must be an owner or security manager for the organization to use this endpoint.
+
+OAuth app tokens and personal access tokens (classic) need the `security_events` scope to use this endpoint.
+
+```js
+octokit.rest.campaigns.getCampaignSummary({
+  org,
+  campaign_number,
+});
+```
+
+## Parameters
+
+<table>
+  <thead>
+    <tr>
+      <th>name</th>
+      <th>required</th>
+      <th>description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>org</td><td>yes</td><td>
+
+The organization name. The name is not case sensitive.
+
+</td></tr>
+<tr><td>campaign_number</td><td>yes</td><td>
+
+The campaign number.
+
+</td></tr>
+  </tbody>
+</table>
+
+See also: [GitHub Developer Guide documentation](https://docs.github.com/rest/campaigns/campaigns#get-a-campaign-for-an-organization).

docs/campaigns/listOrgCampaigns.md

@@ -0,0 +1,67 @@
+---
+name: List campaigns for an organization
+example: octokit.rest.campaigns.listOrgCampaigns({ org })
+route: GET /orgs/{org}/campaigns
+scope: campaigns
+type: API method
+---
+
+# List campaigns for an organization
+
+Lists campaigns in an organization.
+
+The authenticated user must be an owner or security manager for the organization to use this endpoint.
+
+OAuth app tokens and personal access tokens (classic) need the `security_events` scope to use this endpoint.
+
+```js
+octokit.rest.campaigns.listOrgCampaigns({
+  org,
+});
+```
+
+## Parameters
+
+<table>
+  <thead>
+    <tr>
+      <th>name</th>
+      <th>required</th>
+      <th>description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>org</td><td>yes</td><td>
+
+The organization name. The name is not case sensitive.
+
+</td></tr>
+<tr><td>page</td><td>no</td><td>
+
+The page number of the results to fetch. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
+
+</td></tr>
+<tr><td>per_page</td><td>no</td><td>
+
+The number of results per page (max 100). For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
+
+</td></tr>
+<tr><td>direction</td><td>no</td><td>
+
+The direction to sort the results by.
+
+</td></tr>
+<tr><td>state</td><td>no</td><td>
+
+If specified, only campaigns with this state will be returned.
+
+</td></tr>
+<tr><td>sort</td><td>no</td><td>
+
+The property by which to sort the results.
+
+</td></tr>
+  </tbody>
+</table>
+
+See also: [GitHub Developer Guide documentation](https://docs.github.com/rest/campaigns/campaigns#list-campaigns-for-an-organization).

docs/campaigns/updateCampaign.md

@@ -0,0 +1,83 @@
+---
+name: Update a campaign
+example: octokit.rest.campaigns.updateCampaign({ org, campaign_number })
+route: PATCH /orgs/{org}/campaigns/{campaign_number}
+scope: campaigns
+type: API method
+---
+
+# Update a campaign
+
+Updates a campaign in an organization.
+
+The authenticated user must be an owner or security manager for the organization to use this endpoint.
+
+OAuth app tokens and personal access tokens (classic) need the `security_events` scope to use this endpoint.
+
+```js
+octokit.rest.campaigns.updateCampaign({
+  org,
+  campaign_number,
+});
+```
+
+## Parameters
+
+<table>
+  <thead>
+    <tr>
+      <th>name</th>
+      <th>required</th>
+      <th>description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>org</td><td>yes</td><td>
+
+The organization name. The name is not case sensitive.
+
+</td></tr>
+<tr><td>campaign_number</td><td>yes</td><td>
+
+The campaign number.
+
+</td></tr>
+<tr><td>name</td><td>no</td><td>
+
+The name of the campaign
+
+</td></tr>
+<tr><td>description</td><td>no</td><td>
+
+A description for the campaign
+
+</td></tr>
+<tr><td>managers</td><td>no</td><td>
+
+The logins of the users to set as the campaign managers. At this time, only a single manager can be supplied.
+
+</td></tr>
+<tr><td>team_managers</td><td>no</td><td>
+
+The slugs of the teams to set as the campaign managers.
+
+</td></tr>
+<tr><td>ends_at</td><td>no</td><td>
+
+The end date and time of the campaign, in ISO 8601 format':' YYYY-MM-DDTHH:MM:SSZ.
+
+</td></tr>
+<tr><td>contact_link</td><td>no</td><td>
+
+The contact link of the campaign. Must be a URI.
+
+</td></tr>
+<tr><td>state</td><td>no</td><td>
+
+Indicates whether a campaign is open or closed
+
+</td></tr>
+  </tbody>
+</table>
+
+See also: [GitHub Developer Guide documentation](https://docs.github.com/rest/campaigns/campaigns#update-a-campaign).

docs/issues/create.md

@@ -79,7 +79,7 @@ Logins for Users to assign to this issue. _NOTE: Only users with push access can
 </td></tr>
 <tr><td>type</td><td>no</td><td>
 
-The name of the issue type to associate with this issue.
+The name of the issue type to associate with this issue. _NOTE: Only users with push access can set the type for new issues. The type is silently dropped otherwise._
 
 </td></tr>
   </tbody>

docs/issues/update.md

@@ -91,7 +91,7 @@ Usernames to assign to this issue. Pass one or more user logins to _replace_ the
 </td></tr>
 <tr><td>type</td><td>no</td><td>
 
-The name of the issue type to associate with this issue or use `null` to remove the current issue type.
+The name of the issue type to associate with this issue or use `null` to remove the current issue type. Only users with push access can set the type for issues. Without push access to the repository, type changes are silently dropped.
 
 </td></tr>
   </tbody>

docs/orgs/createIssueType.md

@@ -12,6 +12,9 @@ Create a new issue type for an organization.
 
 You can find out more about issue types in [Managing issue types in an organization](https://docs.github.com/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization).
 
+To use this endpoint, the authenticated user must be an administrator for the organization. OAuth app tokens and
+personal access tokens (classic) need the `admin:org` scope to use this endpoint.
+
 ```js
 octokit.rest.orgs.createIssueType({
   org,
@@ -45,11 +48,6 @@ Name of the issue type.
 
 Whether or not the issue type is enabled at the organization level.
 
-</td></tr>
-<tr><td>is_private</td><td>no</td><td>
-
-Whether or not the issue type is restricted to issues in private repositories.
-
 </td></tr>
 <tr><td>description</td><td>no</td><td>