diff --git a/.github/workflows/confirm-internal-staff-work-in-docs.yml b/.github/workflows/confirm-internal-staff-work-in-docs.yml
index 76406163c4..cf10eacc96 100644
--- a/.github/workflows/confirm-internal-staff-work-in-docs.yml
+++ b/.github/workflows/confirm-internal-staff-work-in-docs.yml
@@ -61,7 +61,7 @@ jobs:
owner: 'github',
repo: 'docs-internal',
title: `@${context.payload.sender.login} confirm that \#${issueNo} should be in the public github/docs repo`,
- body: `@${context.payload.sender.login} opened https://github.com/github/docs/issues/${issueNo} publicly in the github/docs repo, instead of the private github/docs-internal repo.\n\n@${context.payload.sender.login}, please confirm that this belongs in the public repo and that no sensitive information was disclosed by commenting below and closing the issue.\n\nIf this was not intentional and sensitive information was shared, please delete https://github.com/github/docs/issues/${issueNo} and notify us in the \#docs-open-source channel.\n\nThanks! \n\n/cc @github/docs @github/docs-engineering`,
+ body: `@${context.payload.sender.login} opened https://github.com/github/docs/issues/${issueNo} publicly in the github/docs repo, instead of the private github/docs-internal repo.\n\n@${context.payload.sender.login}, please confirm that this belongs in the public repo and that no sensitive information was disclosed by commenting below and closing the issue.\n\nIf this was not intentional and sensitive information was shared, please delete https://github.com/github/docs/issues/${issueNo} and notify us in the \#docs-open-source channel.\n\nThanks!`,
labels: ['OS confirmation'],
});
diff --git a/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png b/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png
index cc5e7a3d80..6d44a12268 100644
Binary files a/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png and b/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png differ
diff --git a/assets/images/help/settings/password_recovery_page.png b/assets/images/enterprise/settings/password-recovery-page.png
similarity index 100%
rename from assets/images/help/settings/password_recovery_page.png
rename to assets/images/enterprise/settings/password-recovery-page.png
diff --git a/assets/images/help/2fa/2fa-password-reset.png b/assets/images/help/2fa/2fa-password-reset.png
new file mode 100644
index 0000000000..72b82bb4ae
Binary files /dev/null and b/assets/images/help/2fa/2fa-password-reset.png differ
diff --git a/assets/images/help/repository/code-scanning-free-text-search-areas.png b/assets/images/help/repository/code-scanning-free-text-search-areas.png
new file mode 100644
index 0000000000..0799feb0a8
Binary files /dev/null and b/assets/images/help/repository/code-scanning-free-text-search-areas.png differ
diff --git a/assets/images/help/repository/code-scanning-search-alerts.png b/assets/images/help/repository/code-scanning-search-alerts.png
new file mode 100644
index 0000000000..e274f632dd
Binary files /dev/null and b/assets/images/help/repository/code-scanning-search-alerts.png differ
diff --git a/assets/images/help/settings/password-recovery-email-request.png b/assets/images/help/settings/password-recovery-email-request.png
index 557ef8364a..46d2a79f9f 100644
Binary files a/assets/images/help/settings/password-recovery-email-request.png and b/assets/images/help/settings/password-recovery-email-request.png differ
diff --git a/assets/images/help/settings/password-recovery-page.png b/assets/images/help/settings/password-recovery-page.png
new file mode 100644
index 0000000000..db5d73182d
Binary files /dev/null and b/assets/images/help/settings/password-recovery-page.png differ
diff --git a/assets/images/help/sponsors/access-github-sponsors-dashboard.png b/assets/images/help/sponsors/access-github-sponsors-dashboard.png
index a7744e73f7..6ba167ecad 100644
Binary files a/assets/images/help/sponsors/access-github-sponsors-dashboard.png and b/assets/images/help/sponsors/access-github-sponsors-dashboard.png differ
diff --git a/assets/images/help/sponsors/draft-tier-edit.png b/assets/images/help/sponsors/draft-tier-edit.png
new file mode 100644
index 0000000000..0bfec63a49
Binary files /dev/null and b/assets/images/help/sponsors/draft-tier-edit.png differ
diff --git a/assets/images/help/sponsors/recommended-rewards.png b/assets/images/help/sponsors/recommended-rewards.png
new file mode 100644
index 0000000000..8decf45038
Binary files /dev/null and b/assets/images/help/sponsors/recommended-rewards.png differ
diff --git a/assets/images/help/sponsors/tier-editor-button.png b/assets/images/help/sponsors/tier-editor-button.png
new file mode 100644
index 0000000000..1bed58ebdf
Binary files /dev/null and b/assets/images/help/sponsors/tier-editor-button.png differ
diff --git a/assets/images/help/stars/starring-a-repository.png b/assets/images/help/stars/starring-a-repository.png
new file mode 100644
index 0000000000..017148bce9
Binary files /dev/null and b/assets/images/help/stars/starring-a-repository.png differ
diff --git a/assets/images/help/stars/stars_filter_topic.png b/assets/images/help/stars/stars_filter_topic.png
new file mode 100644
index 0000000000..8902c08c46
Binary files /dev/null and b/assets/images/help/stars/stars_filter_topic.png differ
diff --git a/assets/images/help/stars/unstarring-a-repository.png b/assets/images/help/stars/unstarring-a-repository.png
new file mode 100644
index 0000000000..16750ad043
Binary files /dev/null and b/assets/images/help/stars/unstarring-a-repository.png differ
diff --git a/components/DefaultLayout.tsx b/components/DefaultLayout.tsx
index ba82925984..d740f93263 100644
--- a/components/DefaultLayout.tsx
+++ b/components/DefaultLayout.tsx
@@ -38,6 +38,7 @@ export const DefaultLayout = (props: Props) => {
{page.languageVariants.map((languageVariant) => {
return (
{
) : (
-
+
)}
diff --git a/components/article/ArticleVersionPicker.tsx b/components/article/ArticleVersionPicker.tsx
new file mode 100644
index 0000000000..0ab7bcc300
--- /dev/null
+++ b/components/article/ArticleVersionPicker.tsx
@@ -0,0 +1,58 @@
+import Link from 'next/link'
+import { useRouter } from 'next/router'
+import { Dropdown } from '@primer/components'
+
+import { useMainContext } from 'components/context/MainContext'
+import { useVersion } from 'components/hooks/useVersion'
+import { useTranslation } from 'components/hooks/useTranslation'
+
+export const ArticleVersionPicker = () => {
+ const router = useRouter()
+ const { currentVersion } = useVersion()
+ const { allVersions, page, enterpriseServerVersions } = useMainContext()
+ const { t } = useTranslation('pages')
+
+ if (page.permalinks && page.permalinks.length <= 1) {
+ return null
+ }
+
+ return (
+
{
)}
>
-
+
{grandchildTitle}
diff --git a/content/actions/guides/building-and-testing-xamarin-applications.md b/content/actions/guides/building-and-testing-xamarin-applications.md
index dc5108d731..5c1e54b208 100644
--- a/content/actions/guides/building-and-testing-xamarin-applications.md
+++ b/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -24,7 +24,7 @@ topics:
This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. The workflow you create will allow you to see when commits to a pull request cause build or test failures against your default branch; this approach can help ensure that your code is always healthy.
-{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation:
* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
@@ -41,7 +41,7 @@ We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML
### Bulding Xamarin.iOS apps
-The example below demonstrates how to change the default Xamarin bundle and build a Xamarin.iOS application.
+The example below demonstrates how to change the default Xamarin SDK versions and build a Xamarin.iOS application.
{% raw %}
```yaml
@@ -55,34 +55,33 @@ jobs:
runs-on: macos-latest
steps:
- - uses: actions/checkout@v2
- - name: Select default Xamarin bundle to 6_12_6
- run: |
- XAMARIN_SDK=6_12_6
- $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+ - uses: actions/checkout@v2
+ - name: Set default Xamarin SDK versions
+ run: |
+ $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
+
+ - name: Set default Xcode 12.3
+ run: |
+ XCODE_ROOT=/Applications/Xcode_12.3.0.app
+ echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+ sudo xcode-select -s $XCODE_ROOT
- - name: Set default Xcode 12.3
- run: |
- XCODE_ROOT=/Applications/Xcode_12.3.0.app
- echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
- sudo xcode-select -s $XCODE_ROOT
+ - name: Setup .NET Core SDK 5.0.x
+ uses: actions/setup-dotnet@v1
+ with:
+ dotnet-version: '5.0.x'
- - name: Setup .NET Core SDK 5.0.x
- uses: actions/setup-dotnet@v1
- with:
- dotnet-version: '5.0.x'
+ - name: Install dependencies
+ run: nuget restore
- - name: Install dependencies
- run: nuget restore
-
- - name: Build
- run: msbuild /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+ - name: Build
+ run: msbuild /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
```
{% endraw %}
### Bulding Xamarin.Android apps
-The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+The example below demonstrates how to change default Xamarin SDK versions and build a Xamarin.Android application.
{% raw %}
```yaml
@@ -96,22 +95,21 @@ jobs:
runs-on: macos-latest
steps:
- - uses: actions/checkout@v2
- - name: Select default Xamarin bundle to 6_12_6
- run: |
- XAMARIN_SDK=6_12_6
- $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+ - uses: actions/checkout@v2
+ - name: Set default Xamarin SDK versions
+ run: |
+ $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.10 --android=10.2
- - name: Setup .NET Core SDK 5.0.x
- uses: actions/setup-dotnet@v1
- with:
- dotnet-version: '5.0.x'
+ - name: Setup .NET Core SDK 5.0.x
+ uses: actions/setup-dotnet@v1
+ with:
+ dotnet-version: '5.0.x'
- - name: Install dependencies
- run: nuget restore
+ - name: Install dependencies
+ run: nuget restore
- - name: Build
- run: msbuild /t:PackageForAndroid /p:Configuration=Debug
+ - name: Build
+ run: msbuild /t:PackageForAndroid /p:Configuration=Debug
```
{% endraw %}
diff --git a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index 13af927006..89e5581813 100644
--- a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -77,8 +77,8 @@ The following operating systems are supported for the self-hosted runner applica
#### Linux
-- Red Hat Enterprise Linux 7
-- CentOS 7
+- Red Hat Enterprise Linux 7 or later
+- CentOS 7 or later
- Oracle Linux 7
- Fedora 29 or later
- Debian 9 or later
diff --git a/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index e511962c4d..24195f507f 100644
--- a/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -20,7 +20,7 @@ topics:
Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.product.product_location %}.
-When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains.
+When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
{% if currentVersion == "enterprise-server@2.22" %}
To use Docker with {% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
diff --git a/content/admin/index.md b/content/admin/index.md
index 8bc62e9e4b..4c0e68c0a6 100644
--- a/content/admin/index.md
+++ b/content/admin/index.md
@@ -22,7 +22,7 @@ featuredLinks:
- '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
- '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
popular:
- - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+ - '{% if currentVersion == "github-ae@latest" %}/admin/release-notes{% endif %}'
- '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
- '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
- '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
@@ -50,14 +50,3 @@ children:
- /release-notes
- /all-releases
---
-
-
-
-
-
-
-
-
-
-
-
diff --git a/content/admin/overview/about-upgrades-to-new-releases.md b/content/admin/overview/about-upgrades-to-new-releases.md
index f36e855192..fbcaefad55 100644
--- a/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/content/admin/overview/about-upgrades-to-new-releases.md
@@ -45,5 +45,5 @@ To upgrade your enterprise to a new release, see "[Release notes](/enterprise-se
- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the `github/roadmap` repository
{% if currentVersion == "github-ae@latest" %}
-- [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/overview/github-ae-release-notes)
+- [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes)
{% endif %}
diff --git a/content/admin/overview/github-ae-release-notes.md b/content/admin/overview/github-ae-release-notes.md
deleted file mode 100644
index dbd6bc961a..0000000000
--- a/content/admin/overview/github-ae-release-notes.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: GitHub AE release notes
-intro: March 1, 2021
-versions:
- github-ae: '*'
----
-
-### Features
-
-#### {% data variables.product.prodname_actions %} beta
-
-[{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
-
-{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} uses a new [{% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners), only available for {% data variables.product.product_name %}, that enables you to customize the size, image, and networking configuration of the runners. These runners are a finished-service CI compute environment with auto-scaling and management, fully managed by {% data variables.product.company_short %}. During the beta, the use {% data variables.actions.hosted_runner %}s is free of charge. For more information, see "[Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)."
-
-Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.product.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log.
-
-#### {% data variables.product.prodname_registry %} beta
-
-[{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with {% data variables.product.prodname_actions %}, APIs, and webhooks. Create an [end-to-end DevOps workflow](/github-ae@latest/packages/quickstart) that includes your code, continuous integration, and deployment solutions. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages)."
-
-During this beta, {% data variables.product.prodname_registry %} is free of charge to {% data variables.product.product_name %} customers.
-
-#### {% data variables.product.prodname_GH_advanced_security %} beta
-
-{% data variables.product.prodname_GH_advanced_security %} is available in beta and includes both {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. Repository administrators and organization owners can opt into {% data variables.product.prodname_advanced_security %} features in the settings for a repository or organization, within the **Security and analysis** tab. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
-
-During this beta, {% data variables.product.prodname_advanced_security %} features are free of charge to {% data variables.product.product_name %} customers.
-
-#### Manage teams from your identity provider (IdP)
-
-Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-
-#### IP allow lists beta
-
-Enterprise and organization owners can now use IP allow lists to restrict traffic to the enterprise or specific organizations. After you configure an IP allow list, only visitors from IP addresses on the list are permitted to access the resources protected by the list.
-
-This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the {% data variables.product.product_name %} tenant.
-
-For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
-
-#### Pull request auto-merge
-
-With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements (like missing approvals or pending or failing required status checks). For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
-
-### Changes
-
-#### Developer changes
-
-- [Organization owners can now disable publication](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites.
-- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).
-- When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`.
-- You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory.
-- It’s now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#".
-
-##### Administration changes
-
-- Enterprise owners can now [publish a mandatory message](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-mandatory-message). The message is shown to all users and they must acknowledge it. This can be used to display important information, terms of service or policies.
-- The {% data variables.product.prodname_github_app%} single file path permission can now [support up to ten files](/developers/apps/creating-a-github-app-using-url-parameters).
-- When configuring a {% data variables.product.prodname_github_app%}, the authorization callback URL is a required field. Now we will permit the integrator to specify multiple callback URLs. {% data variables.product.product_name %} denies authorization if the callback URL from the request is not listed.
-- A [new API endpoint](/rest/reference/apps#create-a-scoped-access-token) enables the exchange of a user to server token for a user to server token scoped to specific repositories.
-- Events are now logged in the audit log on [promoting a team member to be a team maintainer and on demoting a team maintainer to be a team member](/admin/user-management/audited-actions#teams).
-- The [OAuth device authorization flow](/developers/apps/authorizing-oauth-apps#device-flow) is now supported. This allows any CLI client or developer tool to authenticate using a secondary system.
-- A user can no longer delete their account if SCIM provisioning is enabled.
-
-##### Default branch renaming
-
-Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."
-
-Existing repositories are unaffected by these settings, and their default branch name will not be changed.
-
-This change is one of many changes {% data variables.product.company_short %} is making to support projects and maintainers that want to rename their default branch. To learn more, see [github/renaming](https://github.com/github/renaming).
-
-
-### Bug fixes
-- Users can no longer set a backup email address on their profile. Their email address is set through the IdP only.
-- You can no longer enable two-factor authentication after configuring authentication through your IdP.
-- {% data variables.product.product_name %} can now connect to Azure Boards.
-- Version headers were missing from the APIs, and have now been set to "GitHub AE."
-- Links to documentation have been fixed.
-- Configuration of audit log forwarding within the enterprise's settings was failing.
-- Navigating to gists could result in a 500 error.
-- The Support email or URL was failing to save. It now saves after a period of a few minutes.
-- Organization level pull request templates were not being applied to all pull requests in the organization.
-
-### Known issues
-
-- Geographic location data is not shown in the audit log. Location information can otherwise be discerned from the IP address associated with each event.
-- The link to {% data variables.product.prodname_registry %} from a repository page shows an incorrect search page when that repository does not have any packages.
diff --git a/content/admin/overview/index.md b/content/admin/overview/index.md
index 9f047fd8bd..7c88265d86 100644
--- a/content/admin/overview/index.md
+++ b/content/admin/overview/index.md
@@ -8,6 +8,7 @@ versions:
github-ae: '*'
children:
- /about-github-ae
+ - /about-upgrades-to-new-releases
- /about-data-residency
- /about-enterprise-accounts
- /managing-your-github-enterprise-license
@@ -15,6 +16,5 @@ children:
- /about-upgrades-to-new-releases
- /system-overview
- /about-the-github-enterprise-api
- - /github-ae-release-notes
---
For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/content/admin/release-notes.md b/content/admin/release-notes.md
index 7dfc63a71c..da80bfef2a 100644
--- a/content/admin/release-notes.md
+++ b/content/admin/release-notes.md
@@ -1,11 +1,12 @@
---
title: Release notes
-intro: 'The release notes for {{ allVersions[currentVersion].versionTitle }}.'
layout: release-notes
versions:
enterprise-server: '*'
+ github-ae: '*'
topics:
- Enterprise
- Upgrades
+redirect_from:
+ - /admin/overview/github-ae-release-notes
---
-
diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
index 4ea6d19864..1ed54604f3 100644
--- a/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
+++ b/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
@@ -8,7 +8,7 @@ versions:
enterprise-server: '*'
type: how_to
topics:
- - 2fa
+ - 2FA
- Enterprise
- Organizations
- Policies
diff --git a/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md b/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
index 04ce67f74f..e10c1faaf2 100644
--- a/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
+++ b/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage
- /articles/about-billing-for-git-large-file-storage
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
index 85993efc3b..4be4f764ca 100644
--- a/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
+++ b/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/downgrading-storage-and-bandwidth-for-an-organization/
- /articles/downgrading-git-large-file-storage
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 0578e50af7..9768341301 100644
--- a/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/purchasing-additional-storage-and-bandwidth-for-an-organization/
- /articles/upgrading-git-large-file-storage
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index dc767353c3..bd4ba1f153 100644
--- a/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/viewing-storage-and-bandwidth-usage-for-an-organization/
- /articles/viewing-your-git-large-file-storage-usage
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 4f8e331423..883625b2e6 100644
--- a/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -4,6 +4,7 @@ intro: 'If you want to use {% data variables.product.prodname_actions %} beyond
product: '{% data reusables.gated-features.actions %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index 8e1a45628e..f0dd743d24 100644
--- a/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -4,6 +4,7 @@ intro: 'You can set a spending limit for {% data variables.product.prodname_acti
product: '{% data reusables.gated-features.actions %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index c63d01c376..36ff3ac4bb 100644
--- a/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -4,6 +4,7 @@ intro: 'You can view details of your usage of minutes and storage for {% data va
product: '{% data reusables.gated-features.actions %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/viewing-your-github-actions-usage
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md b/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
index 4aa29f92ff..10d829e631 100644
--- a/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
+++ b/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace
- /articles/about-billing-for-github-marketplace
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
index 59ae7b8013..9f310b8ca2 100644
--- a/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
+++ b/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/canceling-an-app-for-your-organization/
- /articles/canceling-a-github-marketplace-app
- /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index a739c47130..83a0490228 100644
--- a/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/downgrading-an-app-for-your-organization/
- /articles/downgrading-the-billing-plan-for-a-github-marketplace-app
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 4d83567639..0efdad0227 100644
--- a/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/upgrading-an-app-for-your-organization/
- /articles/upgrading-the-billing-plan-for-a-github-marketplace-app
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
index 25c575a3f2..da5b67bed7 100644
--- a/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
+++ b/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
@@ -4,6 +4,7 @@ intro: 'If you want to use {% data variables.product.prodname_registry %} beyond
product: '{% data reusables.gated-features.packages %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/about-billing-for-github-packages
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
index 7b40b6f92c..26bd5275e7 100644
--- a/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
+++ b/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
@@ -4,6 +4,7 @@ intro: 'You can set a spending limit for {% data variables.product.prodname_regi
product: '{% data reusables.gated-features.packages %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index 10c886da3e..0a3c702fd2 100644
--- a/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -4,6 +4,7 @@ intro: 'You can view details of your usage of storage and data transfer for {% d
product: '{% data reusables.gated-features.packages %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/viewing-your-github-packages-usage
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md b/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
index a43b116856..f3bc003210 100644
--- a/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
+++ b/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors
- /articles/about-billing-for-github-sponsors
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/about-billing-for-github-sponsors
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md b/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
index 557893994e..94dfeb62ad 100644
--- a/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
+++ b/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship
- /articles/downgrading-a-sponsorship
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/downgrading-a-sponsorship
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md b/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
index 409f337388..acb8cdb86a 100644
--- a/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
+++ b/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship
- /articles/upgrading-a-sponsorship
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/upgrading-a-sponsorship
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
index 76a0db667c..eebd6ed209 100644
--- a/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
+++ b/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -12,6 +12,7 @@ redirect_from:
- /articles/github-s-billing-plans
- /articles/about-billing-for-github-accounts
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
index 784aa117f6..e831500eb3 100644
--- a/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
+++ b/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
- /articles/about-per-user-pricing
- /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-per-user-pricing
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
index e4f2b52f18..1d683d8778 100644
--- a/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
+++ b/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
@@ -8,6 +8,7 @@ redirect_from:
- /articles/discounted-billing-plans/
- /articles/discounted-subscriptions-for-github-accounts
- /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts
versions:
free-pro-team: '*'
type: reference
diff --git a/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index f2a2c5bf98..4552545a1a 100644
--- a/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -17,6 +17,7 @@ redirect_from:
- /articles/downgrading-your-github-billing-plan/
- /articles/downgrading-your-github-subscription
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription
versions:
free-pro-team: '*'
topics:
diff --git a/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md b/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
index c579ae0546..0c84b370b9 100644
--- a/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
+++ b/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process
- /articles/how-does-upgrading-or-downgrading-affect-the-billing-process
- /github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
index 7052321252..4d90a55f6b 100644
--- a/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
+++ b/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -19,6 +19,7 @@ redirect_from:
- /articles/upgrading-your-github-billing-plan/
- /articles/upgrading-your-github-subscription
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
index 4b76304e93..bd16c7fdea 100644
--- a/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -8,6 +8,7 @@ redirect_from:
- /articles/viewing-and-managing-pending-changes-to-your-billing-plan/
- /articles/viewing-and-managing-pending-changes-to-your-subscription
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security.md b/content/billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security.md
index 0f1c9fc5af..ce8aea83f9 100644
--- a/content/billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security.md
+++ b/content/billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security.md
@@ -4,6 +4,7 @@ intro: 'If you want to use {% data variables.product.prodname_GH_advanced_securi
product: '{% data reusables.gated-features.ghas %}'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/content/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
index c3348bdf2c..978818dd58 100644
--- a/content/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
+++ b/content/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
@@ -4,6 +4,7 @@ intro: 'You can view usage of your {% data variables.product.prodname_GH_advance
permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
product: '{% data reusables.gated-features.ghas %}'
redirect_from:
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage
- /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage
versions:
diff --git a/content/billing/managing-your-github-billing-settings/about-billing-on-github.md b/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
index 2b985d315d..e43e18a807 100644
--- a/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
+++ b/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github
- /articles/about-billing-on-github
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/about-billing-on-github
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
index 00cdd0bc2c..d15fa13689 100644
--- a/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
+++ b/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -13,6 +13,7 @@ redirect_from:
- /articles/adding-information-to-your-organization-s-receipts/
- /articles/adding-information-to-your-receipts
- /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
index 7b5a7f0b39..11e566c03e 100644
--- a/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
+++ b/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -17,6 +17,7 @@ redirect_from:
- /articles/switching-payment-methods-for-your-organization/
- /articles/adding-or-editing-a-payment-method
- /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
index ad5b30ec75..942868a34b 100644
--- a/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
+++ b/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -8,6 +8,7 @@ redirect_from:
- /articles/switching-between-monthly-and-yearly-billing-for-your-organization/
- /articles/changing-the-duration-of-your-billing-cycle
- /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
index 1a31b9b156..d25097660c 100644
--- a/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
+++ b/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -8,6 +8,7 @@ redirect_from:
- /articles/redeeming-a-coupon-for-organizations/
- /articles/redeeming-a-coupon
- /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
index 7aaddadeba..60b469872b 100644
--- a/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ b/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
@@ -9,6 +9,7 @@ redirect_from:
- /articles/removing-a-payment-method-associated-with-your-organization/
- /articles/removing-a-payment-method
- /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 98938e0354..b0cd87e7b2 100644
--- a/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -9,6 +9,7 @@ redirect_from:
- /articles/setting-your-organization-s-billing-email/
- /articles/setting-your-billing-email
- /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
index 67c93522a9..ba51080db7 100644
--- a/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
+++ b/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -6,6 +6,7 @@ redirect_from:
- /articles/what-do-i-do-if-my-card-is-declined/
- /articles/troubleshooting-a-declined-credit-card-charge
- /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
index b9e0e3255a..5f8325dabb 100644
--- a/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
+++ b/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -11,6 +11,7 @@ redirect_from:
- /articles/unlocking-a-locked-organization-account/
- /articles/unlocking-a-locked-account
- /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
index 40c01cd959..2f044896b9 100644
--- a/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
+++ b/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -8,6 +8,7 @@ redirect_from:
- /articles/downloading-receipts-for-organizations/
- /articles/viewing-your-payment-history-and-receipts
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
+ - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
index 12fdf178e6..dcfdf275df 100644
--- a/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
+++ b/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -6,6 +6,7 @@ redirect_from:
- /articles/about-organizations-for-resellers/
- /articles/about-organizations-for-procurement-companies
- /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
+ - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies
versions:
free-pro-team: '*'
type: overview
diff --git a/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index 45525a723a..5acfe27859 100644
--- a/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -5,6 +5,7 @@ redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client
- /articles/creating-and-paying-for-an-organization-on-behalf-of-a-client
- /github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client
+ - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client
versions:
free-pro-team: '*'
type: quick_start
diff --git a/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md b/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
index fbe9713429..b245ff7e29 100644
--- a/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
+++ b/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
@@ -6,6 +6,7 @@ redirect_from:
- /articles/renewing-your-client-s-paid-organization
- /articles/renewing-your-clients-paid-organization
- /github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization
+ - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md b/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
index 14806356d2..9cb24a0a5c 100644
--- a/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -6,6 +6,7 @@ redirect_from:
- /articles/upgrading-or-downgrading-your-client-s-paid-organization
- /articles/upgrading-or-downgrading-your-clients-paid-organization
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization
+ - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization
versions:
free-pro-team: '*'
type: how_to
diff --git a/content/code-security/getting-started/about-securing-your-repository.md b/content/code-security/getting-started/about-securing-your-repository.md
deleted file mode 100644
index 18bf6f2aad..0000000000
--- a/content/code-security/getting-started/about-securing-your-repository.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: About securing your repository
-intro: '{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.'
-redirect_from:
- - /github/administering-a-repository/about-securing-your-repository
- - /articles/securing-your-repository
- - /github/administering-a-repository/securing-your-repository
-versions:
- free-pro-team: '*'
- enterprise-server: '>=3.0'
- github-ae: '*'
-topics:
- - Repositories
----
-
-### Setting up your repository securely
-
-The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
-
-### Securing your repository
-
-{% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-#### Available for all repositories
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
-- **Security policy**
-
- Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-- **Security advisories**
-
- Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage them to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
-
-- **{% data variables.product.prodname_dependabot_alerts %} and security updates**
-
- View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
- and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
- {% endif %}
-
-{% if currentVersion ver_gt "enterprise-server@2.22" %}
-- **{% data variables.product.prodname_dependabot_alerts %}**
-
- View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
- {% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-- **{% data variables.product.prodname_dependabot %} version updates**
-
- Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
- {% endif %}
- {% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-
-#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
- {% endif %}
-
-- **{% data variables.product.prodname_code_scanning_capc %} alerts**
-
- Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
-
-- **{% data variables.product.prodname_secret_scanning_caps %} alerts**
-
- {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
-{% endif %}
-
-{% if currentVersion != "github-ae@latest" %}
-### Exploring dependencies
-{% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore:
-
-* Ecosystems and packages that your repository depends on
-* Repositories and packages that depend on your repository
-
-You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %}
-
-You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
-{% endif %}
diff --git a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index d7bf20ade9..32e3ed3bc3 100644
--- a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -9,8 +9,12 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.1'
github-ae: 'next'
+type: how_to
topics:
- - Security
+ - Security policies
+ - Vulnerabilities
+ - Repositories
+ - Health
---
### About security policies
@@ -54,6 +58,6 @@ By making security reporting instructions clearly available, you make it easy fo
### Further reading
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/content/code-security/getting-started/github-security-features.md b/content/code-security/getting-started/github-security-features.md
new file mode 100644
index 0000000000..6d4fe8d71e
--- /dev/null
+++ b/content/code-security/getting-started/github-security-features.md
@@ -0,0 +1,86 @@
+---
+title: GitHub security features
+intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.'
+versions:
+ free-pro-team: '*'
+ enterprise-server: '>=3.0'
+ github-ae: '*'
+type: overview
+topics:
+ - Repositories
+ - Dependencies
+ - Vulnerabilities
+ - Advanced Security
+---
+
+### About {% data variables.product.prodname_dotcom %}'s security features
+
+{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. Some features are available for all repositories and others are only available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with a {% data variables.product.prodname_GH_advanced_security %} license.
+
+The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Available for all repositories
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+#### Security policy
+
+Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Security advisories
+
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+#### {% data variables.product.prodname_dependabot_alerts %} and security updates
+
+View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
+and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+#### {% data variables.product.prodname_dependabot_alerts %}
+
+View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_dependabot %} version updates
+
+Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
+{% endif %}
+
+#### Dependency graph
+The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
+
+You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
+{% endif %}
+
+#### {% data variables.product.prodname_code_scanning_capc %} alerts
+
+Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+
+#### {% data variables.product.prodname_secret_scanning_caps %} alerts
+
+{% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+#### Dependency review
+
+Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+{% endif %}
+
+### Further reading
+- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
+- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
\ No newline at end of file
diff --git a/content/code-security/getting-started/index.md b/content/code-security/getting-started/index.md
index c9eb0f723f..45311d7a69 100644
--- a/content/code-security/getting-started/index.md
+++ b/content/code-security/getting-started/index.md
@@ -7,9 +7,13 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Repositories
+ - Dependencies
+ - Vulnerabilities
children:
- - /about-securing-your-repository
+ - /github-security-features
+ - /securing-your-repository
+ - /securing-your-organization
- /adding-a-security-policy-to-your-repository
---
diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md
new file mode 100644
index 0000000000..10c35231d4
--- /dev/null
+++ b/content/code-security/getting-started/securing-your-organization.md
@@ -0,0 +1,112 @@
+---
+title: Securing your organization
+intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.'
+permissions: 'Organization owners can configure organization security settings.'
+versions:
+ free-pro-team: '*'
+ enterprise-server: '>=3.0'
+ github-ae: '*'
+type: how_to
+topics:
+ - Organizations
+ - Dependencies
+ - Vulnerabilities
+ - Advanced Security
+---
+
+### Introduction
+This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+Some security features are only available {% if currentVersion == "free-pro-team@latest" %}for public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
+
+### Managing access to your organization
+
+You can use permission levels to control what actions people can take in your organization. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+
+### Creating a default security policy
+
+You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
+
+By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all repositories owned by your organization.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to the feature that you want to manage.
+5. Optionally, select **Automatically enable for new repositories**.
+
+For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+### Managing dependency review
+
+Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. Dependency review is available in all public repositories and in repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Managing {% data variables.product.prodname_dependabot_security_updates %}
+
+For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}.
+5. Optionally, select **Automatically enable for new repositories**.
+
+For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+### Managing {% data variables.product.prodname_dependabot_version_updates %}
+
+You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling version updates](/code-security/supply-chain-security/enabling-and-disabling-version-updates)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Managing {% data variables.product.prodname_GH_advanced_security %}
+
+If your organization has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}.
+5. Optionally, select **Automatically enable for new private repositories**.
+
+For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+### Configuring {% data variables.product.prodname_secret_scanning %}
+{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+
+You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only).
+5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**.
+
+For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% endif %}
+
+### Next steps
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[Exploring security alerts](/code-security/security-overview/exploring-security-alerts)."{% endif %}
+
+You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% if currentVersion == "free-pro-team@latest" %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+{% if currentVersion == "free-pro-team@latest" %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% endif %}
diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md
new file mode 100644
index 0000000000..538d63669d
--- /dev/null
+++ b/content/code-security/getting-started/securing-your-repository.md
@@ -0,0 +1,124 @@
+---
+title: Securing your repository
+intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your repository secure.'
+permissions: 'Repository administrators and organization owners can configure repository security settings.'
+redirect_from:
+ - /github/administering-a-repository/about-securing-your-repository
+ - /github/code-security/getting-started/about-securing-your-repository
+versions:
+ free-pro-team: '*'
+ enterprise-server: '>=3.0'
+ github-ae: '*'
+type: how_to
+topics:
+ - Repositories
+ - Dependencies
+ - Vulnerabilities
+ - Advanced Security
+---
+
+### Introduction
+This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.
+
+Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+Some security features are only available {% if currentVersion == "free-pro-team@latest" %}for public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
+
+### Managing access to your repository
+
+The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+
+From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**, then scroll down to the "Danger Zone."
+
+- To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% if currentVersion == "free-pro-team@latest" %}
+- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+### Setting a security policy
+
+1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**.
+2. Click **Security policy**.
+3. Click **Start setup**.
+4. Add information about supported versions of your project and how to report vulnerabilities.
+
+For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Managing the dependency graph
+
+The dependency graph is automatically generated for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} all public repositories and you can choose to enable it for private repositories.{% else %} all repositories.{% endif %}
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+2. Click **Security & analysis**.
+3. Next to Dependency graph, click **Enable** or **Disable**.
+
+For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Managing {% data variables.product.prodname_dependabot_alerts %}
+
+By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories.
+
+1. Click your profile photo, then click **Settings**.
+2. Click **Security & analysis**.
+3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}.
+
+For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% if currentVersion == "free-pro-team@latest" %}" and "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+### Managing dependency review
+
+Dependency review lets you visualize dependency changes in pull requests before they are merged into your repository. Dependency review is available in all public repositories and in repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+### Managing {% data variables.product.prodname_dependabot_security_updates %}
+
+For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
+
+For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)."
+
+### Managing {% data variables.product.prodname_dependabot_version_updates %}
+
+You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling version updates](/code-security/supply-chain-security/enabling-and-disabling-version-updates)."
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Configuring {% data variables.product.prodname_code_scanning %}
+
+{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+
+You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+### Configuring {% data variables.product.prodname_secret_scanning %}
+{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+
+{% data variables.product.prodname_secret_scanning_caps %} may be enabled for your repository by default depending upon your organization's settings.
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
+4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**.
+
+{% endif %}
+
+### Next steps
+You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% if currentVersion == "free-pro-team@latest" %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+{% if currentVersion == "free-pro-team@latest" %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% endif %}
diff --git a/content/code-security/index.md b/content/code-security/index.md
index 1ef97457a4..ac825b049f 100644
--- a/content/code-security/index.md
+++ b/content/code-security/index.md
@@ -7,7 +7,9 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Repositories
+ - Dependencies
+ - Vulnerabilities
children:
- /getting-started
- /secret-security
diff --git a/content/code-security/secret-security/about-secret-scanning.md b/content/code-security/secret-security/about-secret-scanning.md
index 0760f79fcd..2fb3089672 100644
--- a/content/code-security/secret-security/about-secret-scanning.md
+++ b/content/code-security/secret-security/about-secret-scanning.md
@@ -11,8 +11,10 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: overview
topics:
- - Repositories
+ - Secret scanning
+ - Advanced Security
---
{% data reusables.secret-scanning.beta %}
@@ -77,5 +79,5 @@ To monitor results from {% data variables.product.prodname_secret_scanning %} ac
### Further reading
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
diff --git a/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index 9d43db7cd8..7f590ec28d 100644
--- a/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -10,7 +10,10 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
+ - Secret scanning
+ - Advanced Security
- Repositories
---
diff --git a/content/code-security/secret-security/index.md b/content/code-security/secret-security/index.md
index 5326db7b82..39e0d908c4 100644
--- a/content/code-security/secret-security/index.md
+++ b/content/code-security/secret-security/index.md
@@ -8,6 +8,8 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
+ - Secret scanning
+ - Advanced Security
- Repositories
children:
- /about-secret-scanning
diff --git a/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index 22d8987f8e..d662b959a5 100644
--- a/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -8,7 +8,11 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
+ - Secret scanning
+ - Advanced Security
+ - Alerts
- Repositories
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index a857ac266e..56a42ec52c 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -10,8 +10,11 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: overview
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
---
@@ -59,6 +62,6 @@ You can run third-party analysis tools within {% data variables.product.product_
### Further reading
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
- [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index a8be77ae97..6472b829e9 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -11,8 +11,15 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Actions
+ - Repositories
+ - Pull requests
+ - JavaScript
+ - Python
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index cec538806d..88ad2e7595 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -13,8 +13,16 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Actions
+ - Repositories
+ - C/C++
+ - C#
+ - Java
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 11308d3a67..a348f222a2 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -10,7 +10,8 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Advanced Security
+ - Code scanning
children:
- /about-code-scanning
- /triaging-code-scanning-alerts-in-pull-requests
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index 70798cbef9..fcd488f4fe 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -13,8 +13,12 @@ redirect_from:
- /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning
- /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository
- /code-security/secure-coding/managing-code-scanning-alerts-for-your-repository
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Alerts
+ - Repositories
---
@@ -48,7 +52,7 @@ You need write permission to view a summary of all the alerts for a repository o
{% data reusables.repositories.sidebar-security %}
{% data reusables.repositories.sidebar-code-scanning-alerts %}
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts.
+1. Optionally, use{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.2" %} the free text search box or{% endif %} the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts.
{% endif %}
1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore.
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
@@ -61,12 +65,49 @@ You need write permission to view a summary of all the alerts for a repository o
1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.

+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.2" %}
+### Searching {% data variables.product.prodname_code_scanning %} alerts
+
+You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across:
+- The name of the alert
+- The alert description
+- The alert details (this also includes the information hidden from view by default in the **Show more** collapsible section)
+
+ 
+
+| Supported search | Syntax example | Results |
+| ---- | ---- | ---- |
+| Single word search | `injection` | Returns all the alerts containing the word `injection` |
+| Multiple word search | `sql injection` | Returns all the alerts containing `sql` or `injection` |
+| Exact match search(use double quotes) | `"sql injection"` | Returns all the alerts containing the exact phrase `sql injection` |
+| OR search | `sql OR injection` | Returns all the alerts containing `sql` or `injection` |
+| AND search | `sql AND injection` | Returns all the alerts containing both words `sql` and `injection` |
+
+{% tip %}
+
+**Tips:**
+- The multiple word search is equivalent to an OR search.
+- The AND search will return results where the search terms are found _anywhere_, in any order in the alert name, description, or details.
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-code-scanning-alerts %}
+1. To the right of the **Filters** drop-down menus, type the keywords to search for in the free text search box.
+ 
+2. Press return. The alert listing will contain the open {% data variables.product.prodname_code_scanning %} alerts matching your search criteria.
+
+{% endif %}
+
### Fixing an alert
Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
+You can use{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.2" %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed.
+
Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
@@ -105,7 +146,7 @@ To dismiss or delete alerts:

- Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
+ Optionally, you can use{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.2" %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}

diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index c352049717..09f4af869f 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -10,8 +10,15 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Actions
+ - Repositories
+ - Containers
+ - Java
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
index ef66c08a26..37959ec4ff 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
@@ -14,8 +14,12 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Actions
+ - Repositories
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 5ca44a6f23..a00836e0a5 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -11,8 +11,13 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Pull requests
+ - Alerts
+ - Repositories
---
diff --git a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index e8896cfbd9..3d700d8930 100644
--- a/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -11,8 +11,18 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Actions
+ - Troubleshooting
+ - Repositories
+ - Pull requests
+ - C/C++
+ - C#
+ - Java
---
diff --git a/content/code-security/secure-coding/index.md b/content/code-security/secure-coding/index.md
index 9950164827..20771af9ec 100644
--- a/content/code-security/secure-coding/index.md
+++ b/content/code-security/secure-coding/index.md
@@ -11,7 +11,9 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
children:
- /automatically-scanning-your-code-for-vulnerabilities-and-errors
- /integrating-with-code-scanning
diff --git a/content/code-security/secure-coding/integrating-with-code-scanning/about-integration-with-code-scanning.md b/content/code-security/secure-coding/integrating-with-code-scanning/about-integration-with-code-scanning.md
index 5e2e8d287c..47f95c6a79 100644
--- a/content/code-security/secure-coding/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/content/code-security/secure-coding/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -10,8 +10,12 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: overview
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Webhooks
+ - Integration
---
diff --git a/content/code-security/secure-coding/integrating-with-code-scanning/index.md b/content/code-security/secure-coding/integrating-with-code-scanning/index.md
index 364bb25944..fbb1065f22 100644
--- a/content/code-security/secure-coding/integrating-with-code-scanning/index.md
+++ b/content/code-security/secure-coding/integrating-with-code-scanning/index.md
@@ -11,7 +11,9 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Integration
children:
- /about-integration-with-code-scanning
- /uploading-a-sarif-file-to-github
diff --git a/content/code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/content/code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index 2d36b12501..0c4a5ef2f0 100644
--- a/content/code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/content/code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -12,8 +12,12 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: reference
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Integration
+ - SARIF
---
diff --git a/content/code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/content/code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index be2dd2b57b..31f592307d 100644
--- a/content/code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/content/code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -12,8 +12,15 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Integration
+ - Actions
+ - Repositories
+ - CI
+ - SARIF
---
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index 17fff63d94..b8001a51df 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -8,7 +8,14 @@ versions:
enterprise-server: '>=3.0'
github-ae: '*'
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Repositories
+ - Pull requests
+ - Integration
+ - CI
+ - SARIF
redirect_from:
- /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system
---
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index 60026b0064..025808b169 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -13,8 +13,18 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Integration
+ - CI
+ - Repositories
+ - Pull requests
+ - C/C++
+ - C#
+ - Java
---
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index 1efbc2ef8c..5fe2e55854 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -9,8 +9,13 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - Integration
+ - CI
+ - CodeQL
children:
- /about-codeql-code-scanning-in-your-ci-system
- /running-codeql-cli-in-your-ci-system
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system.md
index 3ca4502685..e36f736b8e 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system.md
@@ -7,9 +7,17 @@ miniTocMaxHeadingLevel: 4
versions:
free-pro-team: '*'
enterprise-server: '>=3.1'
- github-ae: next
+ github-ae: 'next'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Repositories
+ - Pull requests
+ - Integration
+ - CI
+ - SARIF
redirect_from:
- /code-security/secure-coding/running-codeql-cli-in-your-ci-system
---
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index d58df42cb3..e177799902 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -12,8 +12,16 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Repositories
+ - Pull requests
+ - Integration
+ - CI
+ - SARIF
---
@@ -158,7 +166,7 @@ This example is similar to the previous example, however this time the repositor
$ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
```
-1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
{% data reusables.code-scanning.codeql-runner-analyze-example %}
diff --git a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
index b3491880f9..288f962302 100644
--- a/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
+++ b/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -12,8 +12,14 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
- - Security
+ - Advanced Security
+ - Code scanning
+ - CodeQL
+ - Troubleshooting
+ - Integration
+ - CI
---
diff --git a/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 4338399524..e3d8411ea8 100644
--- a/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -4,6 +4,10 @@ intro: 'Vulnerability disclosure is a coordinated effort between security report
miniTocMaxHeadingLevel: 4
versions:
free-pro-team: '*'
+type: overview
+topics:
+ - Security advisories
+ - Vulnerabilities
---
### About disclosing vulnerabilities in the industry
diff --git a/content/code-security/security-advisories/about-github-security-advisories.md b/content/code-security/security-advisories/about-github-security-advisories.md
index 70db6331c7..c214bf09e9 100644
--- a/content/code-security/security-advisories/about-github-security-advisories.md
+++ b/content/code-security/security-advisories/about-github-security-advisories.md
@@ -7,8 +7,11 @@ redirect_from:
- /github/managing-security-vulnerabilities/about-github-security-advisories
versions:
free-pro-team: '*'
+type: overview
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - CVEs
---
{% data reusables.repositories.security-advisory-admin-permissions %}
diff --git a/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md b/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md
index 07fc24a299..7f844c3ef4 100644
--- a/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md
+++ b/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md
@@ -7,8 +7,11 @@ redirect_from:
- /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - Collaboration
---
People with admin permissions to a security advisory can add collaborators to the security advisory.
diff --git a/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md
index 73635560ea..19f4e558a3 100644
--- a/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md
+++ b/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md
@@ -6,8 +6,12 @@ redirect_from:
- /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - Collaboration
+ - Forks
---
### Prerequisites
diff --git a/content/code-security/security-advisories/creating-a-security-advisory.md b/content/code-security/security-advisories/creating-a-security-advisory.md
index dab420dc4a..1a0e0bf4aa 100644
--- a/content/code-security/security-advisories/creating-a-security-advisory.md
+++ b/content/code-security/security-advisories/creating-a-security-advisory.md
@@ -7,8 +7,10 @@ redirect_from:
- /github/managing-security-vulnerabilities/creating-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
---
Anyone with admin permissions to a repository can create a security advisory.
diff --git a/content/code-security/security-advisories/editing-a-security-advisory.md b/content/code-security/security-advisories/editing-a-security-advisory.md
index 8664ab31dc..12dab63f8d 100644
--- a/content/code-security/security-advisories/editing-a-security-advisory.md
+++ b/content/code-security/security-advisories/editing-a-security-advisory.md
@@ -5,8 +5,10 @@ redirect_from:
- /github/managing-security-vulnerabilities/editing-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
---
People with admin permissions to a security advisory can edit the security advisory.
diff --git a/content/code-security/security-advisories/index.md b/content/code-security/security-advisories/index.md
index 08d85d2fb3..ba5b199dde 100644
--- a/content/code-security/security-advisories/index.md
+++ b/content/code-security/security-advisories/index.md
@@ -8,7 +8,10 @@ redirect_from:
versions:
free-pro-team: '*'
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - Repositories
+ - CVEs
children:
- /about-coordinated-disclosure-of-security-vulnerabilities
- /about-github-security-advisories
diff --git a/content/code-security/security-advisories/permission-levels-for-security-advisories.md b/content/code-security/security-advisories/permission-levels-for-security-advisories.md
index a63400c572..56390ba86a 100644
--- a/content/code-security/security-advisories/permission-levels-for-security-advisories.md
+++ b/content/code-security/security-advisories/permission-levels-for-security-advisories.md
@@ -7,8 +7,11 @@ redirect_from:
- /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
versions:
free-pro-team: '*'
+type: reference
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - Permissions
---
### Permissions overview
diff --git a/content/code-security/security-advisories/publishing-a-security-advisory.md b/content/code-security/security-advisories/publishing-a-security-advisory.md
index e009c50cf2..a8d2fb149e 100644
--- a/content/code-security/security-advisories/publishing-a-security-advisory.md
+++ b/content/code-security/security-advisories/publishing-a-security-advisory.md
@@ -7,8 +7,12 @@ redirect_from:
- /github/managing-security-vulnerabilities/publishing-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - CVEs
+ - Repositories
---
diff --git a/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md b/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md
index e1586b3754..5692dbd270 100644
--- a/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md
+++ b/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md
@@ -5,8 +5,11 @@ redirect_from:
- /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
+ - Collaboration
---
People with admin permissions to a security advisory can remove collaborators from the security advisory.
diff --git a/content/code-security/security-advisories/withdrawing-a-security-advisory.md b/content/code-security/security-advisories/withdrawing-a-security-advisory.md
index 79dbae768e..12270c2484 100644
--- a/content/code-security/security-advisories/withdrawing-a-security-advisory.md
+++ b/content/code-security/security-advisories/withdrawing-a-security-advisory.md
@@ -5,8 +5,10 @@ redirect_from:
- /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Vulnerabilities
---
If you publish a security advisory in error, you can withdraw the security advisory by contacting {% data variables.contact.contact_support %}.
diff --git a/content/code-security/security-overview/exploring-security-alerts.md b/content/code-security/security-overview/exploring-security-alerts.md
index ffb1651a8f..4934707319 100644
--- a/content/code-security/security-overview/exploring-security-alerts.md
+++ b/content/code-security/security-overview/exploring-security-alerts.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.security-center %}'
versions:
free-pro-team: '*'
github-ae: 'next'
+type: how_to
+topics:
+ - Security overview
+ - Advanced Security
+ - Alerts
+ - Organizations
+ - Teams
---
{% data reusables.security-center.beta %}
@@ -13,7 +20,7 @@ versions:
You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
-The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)."
+The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
In the security overview, you can view, sort, and filter alerts to understand the security risks in your organization and in specific repositories. You can apply multiple filters to focus on areas of interest. For example, you can identify private repositories that have a high number of {% data variables.product.prodname_dependabot_alerts %} or repositories that have no {% data variables.product.prodname_code_scanning %} alerts.
diff --git a/content/code-security/security-overview/index.md b/content/code-security/security-overview/index.md
index da3b8892a0..121d861380 100644
--- a/content/code-security/security-overview/index.md
+++ b/content/code-security/security-overview/index.md
@@ -5,7 +5,10 @@ intro: 'View, sort, and filter the security alerts from across your organization
product: '{% data reusables.gated-features.security-center %}'
versions:
free-pro-team: '*'
- github-ae: next
+ github-ae: 'next'
+topics:
+ - Security overview
+ - Advanced Security
children:
- /exploring-security-alerts
---
diff --git a/content/code-security/supply-chain-security/index.md b/content/code-security/supply-chain-security/index.md
index 06dd68e360..26f02658df 100644
--- a/content/code-security/supply-chain-security/index.md
+++ b/content/code-security/supply-chain-security/index.md
@@ -9,7 +9,9 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
topics:
- - Security
+ - Dependabot
+ - Dependencies
+ - Repositories
children:
- /understanding-your-software-supply-chain
- /keeping-your-dependencies-updated-automatically
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md
index 8d01da1eae..8967866401 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md
@@ -9,8 +9,13 @@ redirect_from:
- /code-security/supply-chain-security/about-dependabot-version-updates
versions:
free-pro-team: '*'
+type: overview
topics:
+ - Dependabot
+ - Version updates
- Repositories
+ - Dependencies
+ - Pull requests
---
### About {% data variables.product.prodname_dependabot_version_updates %}
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
index e8caa1a624..525ea937dd 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
@@ -8,8 +8,13 @@ redirect_from:
miniTocMaxHeadingLevel: 4
versions:
free-pro-team: '*'
+type: reference
topics:
+ - Dependabot
+ - Version updates
- Repositories
+ - Dependencies
+ - Pull requests
---
### About the *dependabot.yml* file
@@ -944,3 +949,17 @@ registries:
token: ${{secrets.MY_GITHUB_PERSONAL_TOKEN}}
```
{% endraw %}
+
+#### `terraform-registry`
+
+The `terraform-registry` type supports a token.
+
+{% raw %}
+```yaml
+registries:
+ terraform-example:
+ type: terraform-registry
+ url: https://terraform.example.com
+ token: ${{secrets.MY_TERRAFORM_API_TOKEN}}
+```
+{% endraw %}
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md
index 3e7a411b73..31aa2d374c 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md
@@ -7,8 +7,15 @@ redirect_from:
- /code-security/supply-chain-security/customizing-dependency-updates
versions:
free-pro-team: '*'
+type: how_to
topics:
+ - Dependabot
+ - Version updates
+ - Security updates
- Repositories
+ - Dependencies
+ - Pull requests
+ - Vulnerabilities
---
### About customizing dependency updates
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md
index db653a02a7..9ede734d6f 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md
@@ -7,8 +7,13 @@ redirect_from:
- /code-security/supply-chain-security/enabling-and-disabling-version-updates
versions:
free-pro-team: '*'
+type: how_to
topics:
+ - Dependabot
+ - Version updates
- Repositories
+ - Dependencies
+ - Pull requests
---
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md
index 946d617301..0d9fda6298 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md
@@ -7,6 +7,10 @@ versions:
free-pro-team: '*'
topics:
- Repositories
+ - Dependabot
+ - Version updates
+ - Dependencies
+ - Pull requests
children:
- /about-dependabot-version-updates
- /upgrading-from-dependabotcom-to-github-native-dependabot
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md
index 1582a893f2..370462752a 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md
@@ -7,8 +7,12 @@ redirect_from:
- /code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot
versions:
free-pro-team: '*'
+type: how_to
topics:
- Repositories
+ - Dependabot
+ - Version updates
+ - Actions
---
### About {% data variables.product.prodname_dependabot_version_updates %} for actions
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md
index 7e51fb81da..d36e451296 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md
@@ -6,8 +6,12 @@ redirect_from:
- /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates
versions:
free-pro-team: '*'
+type: how_to
topics:
- Repositories
+ - Dependabot
+ - Version updates
+ - Dependencies
---
### Viewing dependencies monitored by {% data variables.product.prodname_dependabot %}
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
index a91e7a3de6..b9e9cdaf5b 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
@@ -6,6 +6,13 @@ redirect_from:
- /code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot
versions:
free-pro-team: '*'
+type: how_to
+topics:
+ - Dependabot
+ - Version updates
+ - Secret store
+ - Repositories
+ - Dependencies
---
### About encrypted secrets for {% data variables.product.prodname_dependabot %}
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md
index b84c596853..e4de9c94be 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md
@@ -6,8 +6,14 @@ redirect_from:
- /code-security/supply-chain-security/managing-pull-requests-for-dependency-updates
versions:
free-pro-team: '*'
+type: how_to
topics:
- Repositories
+ - Version updates
+ - Security updates
+ - Pull requests
+ - Dependencies
+ - Vulnerabilities
---
### About {% data variables.product.prodname_dependabot %} pull requests
diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
index d27aa13db1..476f4ff94c 100644
--- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
+++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -3,8 +3,12 @@ title: Upgrading from Dependabot.com to GitHub-native Dependabot
intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
versions:
free-pro-team: '*'
+type: how_to
topics:
- Repositories
+ - Dependabot
+ - Version updates
+ - Dependencies
redirect_from:
- /code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 0947e29647..28ea3e52fc 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -9,8 +9,13 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: overview
topics:
- - Security
+ - Dependabot
+ - Alerts
+ - Vulnerabilities
+ - Repositories
+ - Dependencies
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
index 248d7bb1de..3192e829c7 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
@@ -8,8 +8,14 @@ redirect_from:
- /code-security/supply-chain-security/about-dependabot-security-updates
versions:
free-pro-team: '*'
+type: overview
topics:
- - Security
+ - Dependabot
+ - Security updates
+ - Vulnerabilities
+ - Repositories
+ - Dependencies
+ - Pull requests
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
index 2a96479ef9..bebdc22998 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
@@ -6,8 +6,13 @@ redirect_from:
- /code-security/supply-chain-security/about-managing-vulnerable-dependencies
versions:
free-pro-team: '*'
+type: overview
topics:
- - Security
+ - Dependabot
+ - Vulnerabilities
+ - Repositories
+ - Dependencies
+ - Pull requests
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index d5471b8dba..fac43820d6 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -7,8 +7,13 @@ redirect_from:
- /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Security advisories
+ - Alerts
+ - Dependabot
+ - Vulnerabilities
+ - CVEs
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md
index 0d764859de..919f28f31b 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md
@@ -11,8 +11,14 @@ redirect_from:
- /code-security/supply-chain-security/configuring-dependabot-security-updates
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Dependabot
+ - Security updates
+ - Alerts
+ - Dependencies
+ - Pull requests
+ - Repositories
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index f1a8d81b33..805dafad46 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
@@ -8,8 +8,14 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: how_to
topics:
- - Security
+ - Dependabot
+ - Alerts
+ - Notifications
+ - Vulnerabilities
+ - Dependencies
+ - Repositories
---
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
index c11b0e35db..d1ebfc41d2 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
@@ -10,6 +10,14 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+topics:
+ - Repositories
+ - Dependabot
+ - Version updates
+ - Dependencies
+ - Pull requests
+ - Vulnerabilities
+ - Alerts
children:
- /about-managing-vulnerable-dependencies
- /browsing-security-vulnerabilities-in-the-github-advisory-database
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
index 1e80a7fc5b..2a2dc7b0ee 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
@@ -8,8 +8,16 @@ redirect_from:
- /code-security/supply-chain-security/troubleshooting-dependabot-errors
versions:
free-pro-team: '*'
+type: how_to
topics:
- - Security
+ - Dependabot
+ - Security updates
+ - Version updates
+ - Repositories
+ - Pull requests
+ - Troubleshooting
+ - Errors
+ - Dependencies
---
### About {% data variables.product.prodname_dependabot %} errors
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 5f9369368b..b73bc87ce1 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -8,8 +8,19 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: how_to
topics:
- - Security
+ - Dependabot
+ - Alerts
+ - Troubleshooting
+ - Errors
+ - Security updates
+ - Dependencies
+ - Vulnerabilities
+ - Dependency graph
+ - Alerts
+ - CVEs
+ - Repositories
---
The results of dependency detection reported by {% data variables.product.product_name %} may be different from the results returned by other tools. There are good reasons for this and it's helpful to understand how {% data variables.product.prodname_dotcom %} determines dependencies for your project.
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index 68507ae33e..e4c339979e 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -10,8 +10,14 @@ shortTitle: Viewing and updating vulnerable dependencies
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: how_to
topics:
- - Security
+ - Dependabot
+ - Security updates
+ - Alerts
+ - Dependencies
+ - Pull requests
+ - Repositories
---
Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% if currentVersion == "free-pro-team@latest" %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts using the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index f3d8594362..4ad228ec86 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -3,7 +3,12 @@ title: About dependency review
intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.'
versions:
free-pro-team: '*'
+type: overview
topics:
+ - Advanced Security
+ - Dependency review
+ - Vulnerabilities
+ - Dependencies
- Pull requests
redirect_from:
- /code-security/supply-chain-security/about-dependency-review
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 23ead0bca8..2db33ec284 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -7,7 +7,10 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: overview
topics:
+ - Dependency graph
+ - Dependencies
- Repositories
---
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
index 5068cac8be..43100e062e 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
@@ -12,7 +12,10 @@ redirect_from:
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+type: how_to
topics:
+ - Dependency graph
+ - Dependencies
- Repositories
---
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
index e1ee0a8325..9e1bca0732 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
@@ -3,6 +3,10 @@ title: Understanding your software supply chain
versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
+topics:
+ - Dependency graph
+ - Dependencies
+ - Repositories
children:
- /about-the-dependency-graph
- /exploring-the-dependencies-of-a-repository
diff --git a/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
index 70bec916fc..d6a393c4fc 100644
--- a/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
+++ b/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -51,8 +51,10 @@ When you create a new codespace, {% data variables.product.prodname_dotcom %} cl
* _install_
* _bootstrap.sh_
* _bootstrap_
+* _script/bootstrap_
* _setup.sh_
* _setup_
+* _script/setup_
If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 8eaaef8458..95710b4ff1 100644
--- a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
title: Creating a default community health file
-intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any public repository owned by the account that does not contain its own file of that type.'
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -16,12 +16,12 @@ topics:
You can add default community health files to the root of a public repository called `.github` that is owned by an organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}.
-{% data variables.product.product_name %} will use and display default files for any public repository owned by the account that does not have its own file of that type in any of the following places:
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
- the root of the repository
- the `.github` folder
- the `docs` folder
-For example, anyone who creates an issue or pull request in a public repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
diff --git a/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md b/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
index 91135e082a..8ebf5b6f86 100644
--- a/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
+++ b/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
@@ -10,7 +10,7 @@ versions:
---
### About {% data variables.product.prodname_desktop %} installation
-You can install {% data variables.product.prodname_desktop %} on supported operating systems. If you have an account on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, you can connect your account to {% data variables.product.prodname_desktop %}. For more information about creating an account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account/)" or contact your {% data variables.product.prodname_enterprise %} site administrator.
+You can install {% data variables.product.prodname_desktop %} on supported operating systems, which currently include {% data variables.desktop.mac-osx-versions %} and {% data variables.desktop.windows-versions %}. If you have an account on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, you can connect your account to {% data variables.product.prodname_desktop %}. For more information about creating an account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account/)" or contact your {% data variables.product.prodname_enterprise %} site administrator.
{% windows %}
diff --git a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index e73617e48b..565436341a 100644
--- a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -14,21 +14,30 @@ topics:
### About {% data variables.product.prodname_github_app %} URL parameters
You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+
* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+{% if currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" %}
+For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+{% endif %}
+
The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
-```
+
+```text
{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite
```
+
{% else %}
-```
+
+```text
{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite
```
+
{% endif %}
The complete list of available query parameters, permissions, and events is listed in the sections below.
@@ -47,11 +56,11 @@ The complete list of available query parameters, permissions, and events is list
`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
-`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
-`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.
+{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
+{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.
`domain` | `string` | The URL of a content reference.
`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
### {% data variables.product.prodname_github_app %} permissions
diff --git a/content/developers/apps/guides/using-content-attachments.md b/content/developers/apps/guides/using-content-attachments.md
index 406cfcaefb..2ad873ee87 100644
--- a/content/developers/apps/guides/using-content-attachments.md
+++ b/content/developers/apps/guides/using-content-attachments.md
@@ -68,7 +68,7 @@ The `body` parameter can contain markdown:
```shell
curl -X POST \
- https://api.github.com/Codertocat/Hello-World/content_references/17/attachments \
+ https://api.github.com/repos/Codertocat/Hello-World/content_references/17/attachments \
-H 'Accept: application/vnd.github.corsair-preview+json' \
-H 'Authorization: Bearer $INSTALLATION_TOKEN' \
-d '{
@@ -160,7 +160,7 @@ To create a Probot App, follow these steps:
await context.github.request({
method: 'POST',
headers: { accept: 'application/vnd.github.corsair-preview+json' },
- url: `/${context.payload.repository.full_name}/content_references/${context.payload.content_reference.id}/attachments`,
+ url: `/repos/${context.payload.repository.full_name}/content_references/${context.payload.content_reference.id}/attachments`,
// Parameters
title: '[A-1234] Error found in core/models.py file',
body: 'You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\nself.save()'
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
index 77bec30c4a..c4897b9add 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
@@ -13,12 +13,33 @@ versions:
{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes:
- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments
-- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program
+- 50,000 {% data variables.product.prodname_actions %} minutes and 50 GB {% data variables.product.prodname_registry %} storage
+- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our [Campus Advisor program](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %}
-Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+To read about how GitHub is used by educators, see [GitHub Education stories.](https://education.github.com/stories)
+
+### {% data variables.product.prodname_campus_program %} terms and conditions
+
+- The license is free for one year and will automatically renew for free every 2 years. You may continue on the free license so long as you continue to operate within the terms of the agreement. Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+
+- Please note that the licenses are for use by the whole school. Internal IT departments, academic research groups, collaborators, students, and other non-academic departments are eligible to use the licenses so long as they are not making a profit from its use. Externally funded research groups that are housed at the university may not use the free licenses.
+
+- You must offer {% data variables.product.prodname_dotcom %} to all of your technical and academic departments and your school’s logo will be shared on the GitHub Education website as a {% data variables.product.prodname_campus_program %} Partner.
+
+- New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see "[Setting up and managing your enterprise](/github/setting-up-and-managing-your-enterprise)." New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support.
+
+
+To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices)
+
+### {% data variables.product.prodname_campus_program %} Application Eligibility
+
+- Often times, a campus CTO/CIO, Dean, Department Chair, or Technology Officer signs the terms of the program on behalf of the campus.
+
+- If your school does not issue email addresses, {% data variables.product.prodname_dotcom %} will reach out to your account administrators with an alternative option to allow you to distribute the student developer pack to your students.
For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page.
-If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)."
+If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. To apply for the Student Developer Pack, [see the application form](https://education.github.com/pack/join).
+
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index faae07451a..9e1c37690f 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -59,8 +59,10 @@ If your course already has a roster, you can update the students on the roster o
{% data reusables.classroom.click-students %}
1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."

-1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers.
- 
+1. Provide the student identifiers for your roster.
+ - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**.
+ - To create a roster manually, type your student identifiers.
+ 
1. Click **Create roster**.

diff --git a/content/github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/content/github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index 12c920336a..78f4c382a7 100644
--- a/content/github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/content/github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ You can choose the default branch for a repository. The default branch is the ba
{% endnote %}
{% endif %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
diff --git a/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 8991e75833..def3ed1b1a 100644
--- a/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -4,7 +4,7 @@ intro: You can change the name of a branch in a repository.
permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.
versions:
free-pro-team: '*'
- enterprise-server: '>=3.2'
+ enterprise-server: '>=3.1'
topics:
- Repositories
redirect_from:
@@ -18,7 +18,7 @@ When you rename a branch on {% data variables.product.product_location %}, any U
Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
-{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name.
### Renaming a branch
diff --git a/content/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository.md b/content/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository.md
index 6dcb49d8c2..aaf3de1a8f 100644
--- a/content/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository.md
+++ b/content/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository.md
@@ -12,7 +12,13 @@ versions:
free-pro-team: '*'
enterprise-server: '>=3.0'
github-ae: '*'
+type: how_to
topics:
+ - Dependabot
+ - Alerts
+ - Advanced Security
+ - Dependency graph
+ - Secret scanning
- Repositories
---
{% if currentVersion == "free-pro-team@latest" %}
@@ -104,5 +110,5 @@ Organization owners and repository administrators can only grant access to view
### Further reading
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
diff --git a/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md b/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md
index fe6a28813c..6660cc035f 100644
--- a/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md
+++ b/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md
@@ -20,6 +20,20 @@ Organization owners can restrict the ability to change repository visibility to
We recommend reviewing the following caveats before you change the visibility of a repository.
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+
+{% warning %}
+
+**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network.
+
+- Wait for a period of reduced activity on {% data variables.product.product_location %}.
+
+- Contact your {% if enterpriseServerVersions contains currentVersion %}site administrator{% elsif currentVersion == "github-ae@latest" %}enterprise owner{% endif %} before proceeding. Your {% if enterpriseServerVersions contains currentVersion %}site administrator{% elsif currentVersion == "github-ae@latest" %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance.
+
+{% endwarning %}
+
+{% endif %}
+
#### Making a repository private
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %}
@@ -52,7 +66,7 @@ We recommend reviewing the following caveats before you change the visibility of
* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."
* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features.
-For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %}
+For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %}
{% endif %}
diff --git a/content/github/authenticating-to-github/index.md b/content/github/authenticating-to-github/index.md
index da0c8d0f60..b148d49abb 100644
--- a/content/github/authenticating-to-github/index.md
+++ b/content/github/authenticating-to-github/index.md
@@ -18,7 +18,7 @@ versions:
enterprise-server: '*'
github-ae: '*'
topics:
- - 2fa
+ - 2FA
- Identity
- Access management
- Usernames
diff --git a/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index f8170cbe79..f8014fa5e3 100644
--- a/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -21,8 +21,11 @@ topics:
2. Enter the email address associated with your personal {% data variables.product.product_name %} account, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.

3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder.
-4. After clicking on the link in your email, you'll be asked to enter a new password.
- 
+4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**.
+ 
+5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
+ {% if currentVersion == "free-pro-team@latest" %}{% else %}
+ {% endif %}
{% tip %}
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
index 1d606c9943..fdd3188522 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
@@ -8,7 +8,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% if currentVersion == "free-pro-team@latest" %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your {% data variables.product.product_name %} account. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index 29b4e76fc8..dfe25fe708 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -11,7 +11,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 6524b7a8a3..0fd2837baf 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -8,7 +8,7 @@ redirect_from:
versions:
free-pro-team: '*'
topics:
- - 2fa
+ - 2FA
---
{% note %}
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
index f9e9d4ed5b..ba0f98eb02 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -13,7 +13,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
index 3189aa3b15..58e5ea2ad4 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -11,7 +11,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
You can configure two-factor authentication using a mobile app{% if currentVersion == "free-pro-team@latest" %} or via text message{% endif %}. You can also add a security key.
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
index 1230bcb8dc..71f6b4e2d4 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
@@ -7,7 +7,7 @@ redirect_from:
versions:
free-pro-team: '*'
topics:
- - 2fa
+ - 2FA
---
If we don't support two-factor authentication via text message for your country of residence, you can set up authentication via a TOTP mobile application. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
index c733c4d604..c1ef7998b7 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
@@ -8,7 +8,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
We strongly recommend using two-factor authentication to secure your account. If you need to disable 2FA, we recommend re-enabling it as soon as possible.
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md
index 1dde6ff69e..5cb69a8555 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -9,7 +9,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
children:
- /about-two-factor-authentication
- /configuring-two-factor-authentication
diff --git a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 6737e6471c..b488bde6a8 100644
--- a/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -10,7 +10,7 @@ versions:
free-pro-team: '*'
enterprise-server: '*'
topics:
- - 2fa
+ - 2FA
---
{% if currentVersion == "free-pro-team@latest" %}
@@ -46,7 +46,8 @@ If you configured two-factor authentication using a security key, you can use yo
{% if currentVersion == "free-pro-team@latest" %}
### Authenticating with a verified device, SSH token, or personal access token
-If you lose access to the two-factor authentication credentials and don't have your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+
+If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
{% note %}
@@ -56,7 +57,7 @@ If you lose access to the two-factor authentication credentials and don't have y
You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
-{% data reusables.two_fa.username-password %}
+1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**

3. Click **I understand, get started** to request a reset of your authentication settings.
diff --git a/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index be9ea3449d..cd8ea1906a 100644
--- a/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -3,8 +3,13 @@ title: Reviewing dependency changes in a pull request
intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.'
versions:
free-pro-team: '*'
+type: how_to
topics:
- Pull requests
+ - Dependency review
+ - Advanced Security
+ - Vulnerabilities
+ - Dependencies
redirect_from:
- /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
- /github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request
diff --git a/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index a211155626..967292d662 100644
--- a/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -49,9 +49,9 @@ We strongly discourage force pushing, since this changes the history of your rep
**Changing the message of the most recently pushed commit**
1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
-2. Use the `push --force` command to force push over the old commit.
+2. Use the `push --force-with-lease` command to force push over the old commit.
```shell
- $ git push --force example-branch
+ $ git push --force-with-lease example-branch
```
**Changing the message of older or multiple commit messages**
diff --git a/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md b/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md
index d5c788b9fa..5ffcebc578 100644
--- a/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -15,39 +15,49 @@ versions:
topics:
- Repositories
---
-You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.'
+You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.
### About stars
Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
{% if currentVersion == "free-pro-team@latest" %}
-You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
+You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".
{% endif %}
Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.
+### Starring a repository
+
+Starring a repository is a simple two-step process.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. In the top-right corner of the page, click **Star**.
+
+1. Optionally, to unstar a previously starred repository, click **Unstar**.
+
+
### Searching stars
+You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred.
+
+1. Go to your {% data variables.explore.your_stars_page %}.
+1. Use the search bar to find your starred repositories or topics by their name.

-You can use the search bar to quickly find repositories and topics you've starred. The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
+The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
### Sorting and filtering stars
+You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
+
+1. Go to your {% data variables.explore.your_stars_page %}.
+1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.

-
-In the upper-right corner of your stars page, you can sort your starred repositories and topics by recently starred, recently active, and most stars.
-
-On the right side of the page, you can filter your list of starred repositories based on their language.
-
+1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.

-
-### Browsing your friends' stars
-
- In the lower-right corner of the page, you can also browse your friends' stars. You can use this to find new repositories and topics to star.
-
-
+1. To filter your list of stars based on repository or topic, click on the desired option.
+
### Further reading
diff --git a/content/github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git.md b/content/github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git.md
index 5165823fbb..421d52615e 100644
--- a/content/github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/content/github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -95,6 +95,8 @@ Turn on the credential helper so that Git will save your password in memory for
# Set the cache to timeout after 1 hour (setting is in seconds)
```
+For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
+
{% endlinux %}
### Further reading
diff --git a/content/github/getting-started-with-github/learning-about-github/about-github-advanced-security.md b/content/github/getting-started-with-github/learning-about-github/about-github-advanced-security.md
index 3f3e662e15..34e99e77e7 100644
--- a/content/github/getting-started-with-github/learning-about-github/about-github-advanced-security.md
+++ b/content/github/getting-started-with-github/learning-about-github/about-github-advanced-security.md
@@ -29,7 +29,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
{% endif %}
-For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)."
+For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.product_name %}
diff --git a/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index c05df1885b..2fb1200184 100644
--- a/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -141,7 +141,7 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
-If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|---|---|---|
@@ -212,7 +212,7 @@ If you authored any commit(s) present in the commit history for the listed tag o
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
-| [apache/log4j](https://github.com/apache/log4j) | 2.11 | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11) |
+| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
### Further reading
diff --git a/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
index 4fa1d5675f..14a5b1ae0e 100644
--- a/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
+++ b/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
@@ -18,7 +18,7 @@ You can still manage the security and analysis features for individual repositor
{% data reusables.security.security-and-analysis-features-enable-read-only %}
-For an overview of repository-level security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."
+For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
### Enabling or disabling features for existing repositories
diff --git a/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
index 478b73c7c8..a650b3b22c 100644
--- a/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
+++ b/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
@@ -31,7 +31,7 @@ The repository owner has full control of the repository. In addition to the acti
| :- | :- |
| {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %}
-| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %}
| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
| Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" |
diff --git a/content/github/site-policy/dmca-takedown-policy.md b/content/github/site-policy/dmca-takedown-policy.md
index 05b3bb5538..2c42ece488 100644
--- a/content/github/site-policy/dmca-takedown-policy.md
+++ b/content/github/site-policy/dmca-takedown-policy.md
@@ -27,6 +27,8 @@ The DMCA provides a safe harbor for service providers that host user-generated c
The DMCA addresses this issue by creating a [copyright liability safe harbor](https://www.copyright.gov/title17/92chap5.html#512) for internet service providers hosting allegedly infringing user-generated content. Essentially, so long as a service provider follows the DMCA's notice-and-takedown rules, it won't be liable for copyright infringement based on user-generated content. Because of this, it is important for GitHub to maintain its DMCA safe-harbor status.
+The DMCA also prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright.
+
### DMCA Notices In a Nutshell
The DMCA provides two simple, straightforward procedures that all GitHub users should know about: (i) a [takedown-notice](/articles/guide-to-submitting-a-dmca-takedown-notice) procedure for copyright holders to request that content be removed; and (ii) a [counter-notice](/articles/guide-to-submitting-a-dmca-counter-notice) procedure for users to get content reenabled when content is taken down by mistake or misidentification.
@@ -66,23 +68,40 @@ One of the best features of GitHub is the ability for users to "fork" one anothe
GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
-In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing content is larger than one hundred (100) repositories and thus would be difficult to review in its entirety, we may consider disabling the entire network if you state in your notice that, "Based on the representative number of forks you have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing content is larger than one hundred (100) repositories and thus would be difficult to review in its entirety, we may consider disabling the entire network if you state in your notice that, "Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
-### C. What If I Inadvertently Missed the Window to Make Changes?
+### C. What about Circumvention Claims?
+
+The DMCA prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. Given that these types of claims are often highly technical in nature, GitHub requires claimants to provide [detailed information about these claims](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), and we undertake a more extensive review.
+
+A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
+1. What the technical measures are;
+2. How they effectively control access to the copyrighted material; and
+3. How the accused project is designed to circumvent their previously described technological protection measures.
+
+GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
+
+Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
+
+Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.
+
+When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer to connect the repository owner with legal resources, in case the repository owner wishes to obtain third party legal advice.
+
+### D. What If I Inadvertently Missed the Window to Make Changes?
We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.
-### D. Transparency
+### E. Transparency
We believe that transparency is a virtue. The public should know what content is being removed from GitHub and why. An informed public can notice and surface potential issues that would otherwise go unnoticed in an opaque system. We post redacted copies of any legal notices we receive (including original notices, counter notices or retractions) at . We will not publicly publish your personal contact information; we will remove personal information (except for usernames in URLs) before publishing notices. We will not, however, redact any other information from your notice unless you specifically ask us to. Here are some examples of a published [notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) and [counter notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) for you to see what they look like. When we remove content, we will post a link to the related notice in its place.
Please also note that, although we will not publicly publish unredacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it.
-### E. Repeated Infringement
+### F. Repeated Infringement
It is the policy of GitHub, in appropriate circumstances and in its sole discretion, to disable and terminate the accounts of users who may infringe upon the copyrights or other intellectual property rights of GitHub or others.
-### F. Submitting Notices
+### G. Submitting Notices
If you are ready to submit a notice or a counter notice:
- [How to Submit a DMCA Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)
diff --git a/content/github/site-policy/github-acceptable-use-policies.md b/content/github/site-policy/github-acceptable-use-policies.md
index 1867db65ce..b0e0861d23 100644
--- a/content/github/site-policy/github-acceptable-use-policies.md
+++ b/content/github/site-policy/github-acceptable-use-policies.md
@@ -31,7 +31,9 @@ Under no circumstances will Users upload, post, host, execute, or transmit any C
- is or contains false, inaccurate, or intentionally deceptive information that is likely to adversely affect the public interest (including health, safety, election integrity, and civic participation);
-- contains or installs any active malware or exploits, or uses our platform for exploit delivery (such as part of a command and control system); or
+- contains or installs any active malware or exploits, or uses our platform for exploit delivery (such as part of a command and control system);
+
+- shares unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys, including extension of a free license beyond its trial period; or
- infringes any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other right.
diff --git a/content/github/site-policy/github-additional-product-terms.md b/content/github/site-policy/github-additional-product-terms.md
deleted file mode 100644
index 69fb523266..0000000000
--- a/content/github/site-policy/github-additional-product-terms.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: GitHub Additional Product Terms
-versions:
- free-pro-team: '*'
-topics:
- - Policy
- - Legal
----
-
-Version Effective Date: February 22, 2021
-
-When you create an Account, you're given access to lots of different features and products that are all a part of the Service. Because many of these features and products offer different functionality, they may require additional terms and conditions specific to that feature or product. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them.
-
-Your use of the Service is subject to your applicable terms (the "Agreement"). By using additional products and features, you also agree to these Additional Product Terms. Any violation of the Additional Product Terms is a violation of the Agreement. Capitalized terms not defined in the Additional Product Terms will have the meaning given to them in the Agreement.
-
-If you are using GitHub AE, then you may only access the following features and products: Third Party Integrations, Git LFS Support, Pages.
-
-### 1. Marketplace
-
-If you list a Developer Product through GitHub Marketplace, then you must agree to the [GitHub Marketplace Developer Agreement](/github/site-policy/github-marketplace-developer-agreement), prior to submitting the project to be listed.
-
-If you buy Developer Products through GitHub Marketplace, the [GitHub Marketplace Terms of Service](/github/site-policy/github-marketplace-terms-of-service) controls your purchase. The Agreement, as well as the [GitHub Marketplace Terms of Service](/github/site-policy/github-marketplace-terms-of-service), will govern your use of GitHub Marketplace.
-
-### 2. Third Party Integrations
-
-#### a. Creating Applications
-If you create a third-party application or other developer product that collects User Personal Information or User-Generated Content and integrates with the Service through GitHub's API, OAuth mechanism, or otherwise ("Developer Product"), and make it available for other Users, then you must comply with the following requirements:
-- You must comply with this Agreement and the GitHub Privacy Statement.
-- Except as otherwise permitted, such as by law or by a license, you must limit your usage of the User Personal Information or User-Generated Content you collect to that purpose for which the User has authorized its collection.
-- You must take all reasonable security measures appropriate to the risks, such as against accidental or unlawful destruction, or accidental loss, alteration, unauthorized disclosure or access, presented by processing the User Personal Information or User-Generated Content.
-- You must not hold yourself out as collecting any User Personal Information or User-Generated Content on GitHub’s behalf, and provide sufficient notice of your privacy practices to the User, such as by posting a privacy policy.
-- You must provide Users with a method of deleting any User Personal Information or User-Generated Content you have collected through GitHub after it is no longer needed for the limited and specified purposes for which the User authorized its collection, except where retention is required by law or otherwise permitted, such as through a license.
-
-#### b. Using Third-Party Applications
-You may grant a Developer Product authorization to use, access, and disclose the contents of your repositories, including your private repositories. Some Developer Products are available through [GitHub Marketplace](https://github.com/marketplace). Some Developer Products can be used for performing automated tasks, and often times multiple Users may direct the actions of a Developer Product. However, if you purchase and/or set up a Developer Product on your Account, or you are an owner of an Account with an integrated Developer Product, then you will be responsible for the Developer Product's actions that are performed on or through your Account. Please see our [Privacy Statement](/github/site-policy/github-privacy-statement#third-party-applications) for more information about how we share data with Developer Products.
-
-**GitHub makes no warranties of any kind in relation to Developer Products and is not liable for disclosures to third parties that you authorize to access Your Content. Your use of any third-party applications is at your sole risk.**
-
-### 3. Git LFS Support
-
-If you enable Git Large File Storage ("Git LFS") on your Account, you'll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. Your Account comes with a certain amount of bandwidth and storage for use with Git LFS, which can be found in the [Git LFS documentation](/github/managing-large-files/about-storage-and-bandwidth-usage). Git LFS bandwidth and storage usage is displayed within your [account settings](https://github.com/settings/billing). If you want to use Git LFS beyond your allotted bandwidth and storage, then you may [purchase additional data packs](/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage).
-
-### 4. Pages
-
-Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). This hosting service is intended to host static web pages for All Users, but primarily as a showcase for personal and organizational projects.
-
-GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links.
-
-#### a. Bandwidth and Usage Limits
-GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages guidelines](/github/working-with-github-pages/about-github-pages) for more information.
-
-#### b. Prohibited Uses
-Prohibited uses of GitHub Pages include
-- Content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service), [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies) or [Community Guidelines](/github/site-policy/github-community-guidelines)
-- Violent or threatening content or activity
-- Excessive automated bulk activity (for example, spamming)
-- Activity that compromises GitHub users or GitHub services
-- Get-rich-quick schemes
-- Sexually obscene content
-- Content that misrepresents your identity or site purpose
-
-If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://premium.githubsupport.com/). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability.
-
-### 5. Actions and Packages
-
-#### a. Actions Usage
-GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits.
-
-Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). Additionally, Actions should not be used for:
-- cryptomining;
-- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com));
-- the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes;
-- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
-- any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
-
-In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms.
-
-#### b. Packages Usage
-GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
-
-### 6. Learning Lab
-
-**Enrollment.** To complete enrollment in Learning Lab for Organizations, you agree to create a separate organization for Learning Lab purposes, and you authorize us to add Learning Lab course materials to that organization on your behalf.
-
-**Learning Lab Course Materials.** Any course materials GitHub provides are owned solely by GitHub; provided, however, that GitHub grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use. This license grant is subject to any additional open source licensing agreements that may be provided along with the source code. Course materials you create are owned solely by you, provided, however, that you grant to GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run (as applicable) on the Service, such course materials. Your use of GitHub course materials and your creation and storage of your own course materials does not constitute joint ownership in either party's respective intellectual property by the other party.
-
-**Privacy.** Learning Lab may collect personal information. You control what information Learning Lab collects in your GitHub.com profile settings panel. If Learning Lab collects personal information on GitHub's behalf, GitHub will process that information in accordance with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). If you enroll in or are completing a private course through Learning Lab, GitHub may share your enrollment information and course progress through completion with the organization admins. This may include individual data such as your GitHub username, course start date, and course end date. Course completion data may also be presented in aggregate form to help guide improvements to the course content.
-
-### 7. Connect
-
-In order to access GitHub Connect, Customer must have at least one (1) Account on GitHub.com and one (1) licensed instance of the Software. Customer's access to and use of github.com through Connect is governed by its Agreement applicable to its use of the Service. GitHub Connect may be used for performing automated tasks. In addition, multiple Users may direct certain actions with GitHub Connect. Customer is responsible for actions that are performed on or through its Accounts. GitHub may collect information about how Customer uses GitHub Connect to provide and improve the feature. By using GitHub Connect, Customer authorizes GitHub to collect protected data, which includes Private Repository data and User Personal Information (as defined in the GitHub Privacy Statement), from Customer’s Accounts. Customer also authorizes the transfer of identifying instance information to GitHub through GitHub Connect, which information is governed by the GitHub Privacy Statement.
-
-### 8. Sponsors Program
-
-In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms).
-
-### 9. GitHub Advanced Security
-
-GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. If you are using GitHub Advanced Security as part of GitHub Enterprise Cloud, many features of GitHub Advanced Security, including automated code scanning of private repositories, also require the use of GitHub Actions.
-
-### 10. Dependabot Preview
-
-Your use of Dependabot Preview is governed by a separate [Terms of Service](https://dependabot.com/terms) and [Privacy Policy](https://dependabot.com/privacy).
-
-### 11. Spectrum
-
-Your use of Spectrum is governed by the GitHub [Terms of Service](/github/site-policy/github-terms-of-service) and [Privacy Statement](/github/site-policy/github-privacy-statement).
-
-### 12. Advisory Database
-
-#### a. License Grant to Us
-
-We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
-
-#### b. License to the GitHub Advisory Database
-
-The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by .
-
-### 13. GitHub Enterprise Server
-
-#### a. SQL Server Images
-
-You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time.
-
-#### b. Third-party components
-
-The Software includes components licensed to GitHub by third parties, including software whose licenses require GitHub to make the source code for those components available. The source code for such components will be provided upon request.
diff --git a/content/github/site-policy/github-terms-for-additional-products-and-features.md b/content/github/site-policy/github-terms-for-additional-products-and-features.md
new file mode 100644
index 0000000000..4869ce6753
--- /dev/null
+++ b/content/github/site-policy/github-terms-for-additional-products-and-features.md
@@ -0,0 +1,109 @@
+---
+title: GitHub Terms for Additional Products and Features
+redirect_from:
+ - /github/site-policy/github-additional-product-terms
+versions:
+ free-pro-team: '*'
+topics:
+ - Policy
+ - Legal
+---
+
+Version Effective Date: May 26, 2021
+
+When you use GitHub, you may be given access to lots of additional products and features ("Additional Products and Features"). Because many of the Additional Products and Features offer different functionality, specific terms for that product or feature may apply in addition to your main agreement with us—the GitHub Terms of Service, GitHub Corporate Terms of Service, GitHub General Terms, or Microsoft volume licensing agreement (each, the "Agreement"). Below, we've listed those products and features, along with the corresponding additional terms that apply to your use of them.
+
+By using the Additional Products and Features, you also agree to the applicable GitHub Terms for Additional Products and Features listed below. A violation of these GitHub terms for Additional Product and Features is a violation of the Agreement. Capitalized terms not defined here have the meaning given in the Agreement.
+
+**For Enterprise users**
+- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, Learning Lab, Octoshift, Packages and Pages.
+
+- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, Learning Lab, Octoshift, Packages, Pages and SQL Server Images.
+
+- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% if currentVersion == "github-ae@next" %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages.
+
+### Actions
+GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits.
+
+Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, Actions should not be used for:
+- cryptomining;
+- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com));
+- the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes;
+- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
+- any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
+
+In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms.
+
+
+### Advanced Security
+GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details.
+
+Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions.
+
+### Advisory Database
+The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub.
+
+_License Grant to Us_
+
+We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
+
+_License to the GitHub Advisory Database_
+
+The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by .
+
+### Connect
+With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% if currentVersion == "github-ae@next" %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% if currentVersion == "github-ae@next" %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+
+### Dependabot Preview
+You can use Dependabot to keep the packages you use updated to the latest versions. Your use of Dependabot Preview is governed by a separate [Terms of Service](https://dependabot.com/terms) and [Privacy Policy](https://dependabot.com/privacy).
+
+### Learning Lab
+GitHub Learning Lab offers free interactive courses that are built into GitHub with instant automated feedback and help.
+
+*Course Materials.* GitHub owns course materials that it provides and grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use.
+
+Open source license terms may apply to portions of source code provided in the course materials.
+
+You own course materials that you create and grant GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run such course materials.
+
+The use of GitHub course materials and creation and storage of your own course materials do not constitute joint ownership to either party's respective intellectual property.
+
+Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+
+### npm
+npm is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. npm is the registry of record for the JavaScript ecosystem. The npm public registry is free to use but customers are billed if they want to publish private packages or manage private packages using teams. The [npm documentation](https://docs.npmjs.com/) includes details about the limitation of account types and how to manage [private packages](https://docs.npmjs.com/about-private-packages) and [organizations](https://docs.npmjs.com/organizations). Acceptable use of the npm registry is outlined in the [open-source terms](https://www.npmjs.com/policies/open-source-terms). There are supplementary terms for both the npm [solo](https://www.npmjs.com/policies/solo-plan) and [org](https://www.npmjs.com/policies/orgs-plan) plans. The npm [Terms of Use](https://www.npmjs.com/policies/terms) apply to your use of npm.
+
+### Octoshift
+Octoshift is a framework for exporting data from other sources to be imported to the GitHub platform. Octoshift is provided “AS-IS”.
+
+### Packages
+GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. GitHub Packages is billed on a usage basis. The [Packages documentation](/packages/learn-github-packages/introduction-to-github-packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
+
+### Pages
+
+Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects.
+
+GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links.
+
+#### a. Bandwidth and Usage Limits
+GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages guidelines](/github/working-with-github-pages/about-github-pages) for more information.
+
+#### b. Prohibited Uses
+Prohibited uses of GitHub Pages include
+- Content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service), [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies) or [Community Guidelines](/github/site-policy/github-community-guidelines)
+- Violent or threatening content or activity
+- Excessive automated bulk activity (for example, spamming)
+- Activity that compromises GitHub users or GitHub services
+- Get-rich-quick schemes
+- Sexually obscene content
+- Content that misrepresents your identity or site purpose
+
+If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://premium.githubsupport.com/). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability.
+
+### Sponsors Program
+
+GitHub Sponsors allows the developer community to financially support the people and organizations who design, build, and maintain the open source projects they depend on, directly on GitHub. In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+
+### SQL Server Images
+
+You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time.
diff --git a/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index d2a5d0f82f..d2494ab6d9 100644
--- a/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -73,7 +73,10 @@ GitHub exercises little discretion in the process other than determining whether
### Complaints about Anti-Circumvention Technology
-The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}, and include specific information about what content violates that prohibition, what technological measures you had in place, and why the content violates the prohibition.
+The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}. A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
+1. What the technical measures are;
+2. How they effectively control access to the copyrighted material; and
+3. How the accused project is designed to circumvent their previously described technological protection measures.
### How to Submit Your Complaint
diff --git a/content/github/site-policy/index.md b/content/github/site-policy/index.md
index 8b9664b7e4..144b71b8d3 100644
--- a/content/github/site-policy/index.md
+++ b/content/github/site-policy/index.md
@@ -16,7 +16,7 @@ children:
- /global-privacy-practices
- /github-insights-and-data-protection-for-your-organization
- /github-sponsors-additional-terms
- - /github-additional-product-terms
+ - /github-terms-for-additional-products-and-features
- /github-logo-policy
- /github-username-policy
- /submitting-content-removal-requests
@@ -50,4 +50,3 @@ children:
- /github-event-code-of-conduct
- /github-gpl-cooperation-commitment
---
-
diff --git a/content/github/writing-on-github/index.md b/content/github/writing-on-github/index.md
index c5c59645bb..7dfdcaae03 100644
--- a/content/github/writing-on-github/index.md
+++ b/content/github/writing-on-github/index.md
@@ -5,6 +5,7 @@ redirect_from:
- /articles/github-flavored-markdown/
- /articles/writing-on-github/
- /categories/writing-on-github
+intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.'
versions:
free-pro-team: '*'
enterprise-server: '*'
@@ -15,4 +16,3 @@ children:
- /working-with-saved-replies
- /editing-and-sharing-content-with-gists
---
-
diff --git a/content/issues/index.md b/content/issues/index.md
index 2c90a52df9..dcc6bd2276 100644
--- a/content/issues/index.md
+++ b/content/issues/index.md
@@ -1,7 +1,7 @@
---
-title: Issues and Projects
-shortTitle: Issues and Projects
-intro: Use issues and projects to manage your work on {% data variables.product.prodname_dotcom %}
+title: Issues and projects
+shortTitle: Issues and projects
+intro: Use issues and projects to manage your work on {% data variables.product.prodname_dotcom %}.
versions:
free-pro-team: '*'
enterprise-server: '*'
diff --git a/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index af44d60838..a2e911da2f 100644
--- a/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -149,7 +149,7 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security
### Further reading
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %}
- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% if currentVersion != "github-ae@latest" %}
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
diff --git a/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index 1fe4a31162..ef375f63ef 100644
--- a/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -112,7 +112,7 @@ In addition to managing organization-level settings, organization owners have ad
| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** |
| Change a repository's settings | | | | | **X** |
| Manage team and collaborator access to the repository | | | | | **X** |
-| Edit the repository's default branch | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+| Edit the repository's default branch | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** |
| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %}
| Manage webhooks and deploy keys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %}
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index 9f7e9cabc8..c0f268adf8 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -100,7 +100,7 @@ When using an apex domain, we recommend configuring your {% data variables.produ
To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
-After you configure the apex domain, you must to configure a CNAME record with your DNS provider.
+After you configure the apex domain, you must configure a CNAME record with your DNS provider.
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
index ac1383ed32..c6952a580b 100644
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
@@ -45,6 +45,11 @@ Your theme includes default layouts, includes, and stylesheets that will automat
{% data reusables.files.choose-commit-email %}
{% data reusables.files.choose_commit_branch %}
{% data reusables.files.propose_file_change %}
+{% data reusables.files.choose_pull_request %}
+{% data reusables.files.merge_pull_request %}
+{% data reusables.files.write_commit_message_pull_request %}
+{% data reusables.files.confirm_merge %}
+{% data reusables.files.delete_branch %}
### Adding a new post to your site
@@ -64,6 +69,11 @@ Your theme includes default layouts, includes, and stylesheets that will automat
{% data reusables.files.choose-commit-email %}
{% data reusables.files.choose_commit_branch %}
{% data reusables.files.propose_file_change %}
+{% data reusables.files.choose_pull_request %}
+{% data reusables.files.merge_pull_request %}
+{% data reusables.files.write_commit_message_pull_request %}
+{% data reusables.files.confirm_merge %}
+{% data reusables.files.delete_branch %}
Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`.
diff --git a/content/rest/overview/libraries.md b/content/rest/overview/libraries.md
index ae3d3f5e07..e97d3bd1f1 100644
--- a/content/rest/overview/libraries.md
+++ b/content/rest/overview/libraries.md
@@ -101,14 +101,10 @@ Library name | Repository | metacpan Website for the Library
Library name | Repository
|---|---|
-**GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client)
**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)
**GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api)
**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)
-**GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github)
-**GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api)
**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)
-**PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI)
### PowerShell
diff --git a/content/rest/reference/code-scanning.md b/content/rest/reference/code-scanning.md
index 56f7a494cc..11833f581a 100644
--- a/content/rest/reference/code-scanning.md
+++ b/content/rest/reference/code-scanning.md
@@ -7,8 +7,11 @@ versions:
free-pro-team: '*'
enterprise-server: '>=2.22'
github-ae: '*'
+type: reference
topics:
- API
+ - Code scanning
+ - REST
---
{% data reusables.code-scanning.beta %}
diff --git a/content/rest/reference/repos.md b/content/rest/reference/repos.md
index 550c0eec06..b9b984d3c1 100644
--- a/content/rest/reference/repos.md
+++ b/content/rest/reference/repos.md
@@ -369,4 +369,4 @@ Name | Type | Description
``hub.mode``|`string` | **Required**. Either `subscribe` or `unsubscribe`.
``hub.topic``|`string` |**Required**. The URI of the GitHub repository to subscribe to. The path must be in the format of `/{owner}/{repo}/events/{event}`.
``hub.callback``|`string` | The URI to receive the updates to the topic.
-``hub.secret``|`string` | A shared secret key that generates a SHA1 HMAC of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the `X-Hub-Signature` header. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
+``hub.secret``|`string` | A shared secret key that generates a hash signature of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` header{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` header{% endif %}. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
index 7f5f951ecd..035f3d8ec5 100644
--- a/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
+++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -23,6 +23,12 @@ topics:
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+1. If you are setting up tiers for the first time, we recommend you review the suggested tier examples to see how some other open source contributors have set up {% data variables.product.prodname_sponsors %}. Decide whether you want to start with some suggested draft tiers, which you can customize in the tier editor.
+ - To use a suggested tier, select the rewards you'd like to include in your draft tier or tiers. Then, click **Continue to tier editor**.
+ - To create tiers without using with any of the draft suggestions, click **Skip this step**.
+ 
+1. Optionally, to edit a draft tier, find the draft tier and click **Edit**.
+ 
{% data reusables.sponsors.click-add-tier %}
{% data reusables.sponsors.tier-price-description %}
{% data reusables.sponsors.save-tier-draft %}
@@ -33,6 +39,11 @@ topics:
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
{% data reusables.sponsors.edit-tier %}
+ {% note %}
+
+ **Note:** To see ideas of tier descriptions, scroll down.
+
+ {% endnote %}
{% data reusables.sponsors.tier-price-description %}
{% data reusables.sponsors.tier-update %}
{% data reusables.sponsors.retire-tier %}
diff --git a/data/allowed-topics.js b/data/allowed-topics.js
index be77a0493c..d0cafc9144 100644
--- a/data/allowed-topics.js
+++ b/data/allowed-topics.js
@@ -11,132 +11,149 @@
// content and/or content strategy team for review.
module.exports = [
- '2fa',
+ '2FA',
+ 'Access management',
+ 'Accounts',
'Action development',
'Actions',
'Administrator',
'Advanced Security',
+ 'Alerts',
'Amazon ECS',
+ 'Analytics',
'Android',
'Ant',
- 'Analytics',
'API',
'Auditing',
'Authentication',
'Azure App Service',
'Azure Pipelines',
'Backups',
+ 'Billing',
+ 'C/C++',
+ 'C#',
'Cancellation',
'CD',
'CI',
'CircleCI',
+ 'CLI',
'Clustering',
+ 'Code scanning',
+ 'CodeQL',
+ 'Codespaces',
+ 'Collaboration',
+ 'Community',
'Contacting sponsors',
'Containers',
- 'Code scanning',
- 'Codespaces',
+ 'CVEs',
+ 'Dependabot',
+ 'Dependencies',
+ 'Dependency graph',
+ 'Dependency review',
+ 'Desktop',
'Developer',
+ 'Device verification',
+ 'Discounts',
'Discussions',
'Docker',
'Downgrades',
+ 'Early access',
'Education',
- 'Events',
+ 'Enterprise',
'Errors',
+ 'Events',
+ 'Forks',
'Fundamentals',
'Git',
+ 'GitHub Apps',
'GitHub Connect',
+ 'GitHub search',
+ 'GitHub',
'GitLab',
'Google Kubernetes Engine',
'Gradle',
'GraphQL',
+ 'Health',
'High availability',
+ 'Identity',
'Infrastructure',
+ 'Integration',
'iOS',
+ 'Issues',
'Java',
'JavaScript',
'Jenkins',
+ 'Jobs',
+ 'Legal',
+ 'LFS',
'Licensing',
'Logging',
+ 'Maintenance',
'Marketplace',
'Maven',
'Migration',
+ 'Mobile',
'Monitoring',
'Networking',
'Node',
'Nonprofits',
+ 'Notifications',
+ 'OAuth Apps',
'Open Source',
'Organizations',
'Packages',
'Packaging',
- 'Performance',
- 'Powershell',
- 'Pre-receive hooks',
- 'Privacy',
- 'Project management',
- 'Publishing',
- 'Python',
- 'Ruby',
- 'Secret scanning',
- 'Security',
- 'Sponsors',
- 'Sponsors payments',
- 'Sponsors profile',
- 'Storage',
- 'Support',
- 'Swift',
- 'Travis CI',
- 'Upgrades',
- 'User account',
- 'Webhooks',
- 'Workflows',
- 'Access management',
- 'Accounts',
- 'Billing',
- 'CLI',
- 'Codespaces',
- 'Community',
- 'Desktop',
- 'Device verification',
- 'Discounts',
- 'Early access',
- 'Enterprise',
- 'GitHub',
- 'GitHub Apps',
- 'GitHub search',
- 'Identity',
- 'Issues',
- 'Jobs',
- 'Legal',
- 'LFS',
- 'Maintenance',
- 'Marketplace',
- 'Mobile',
- 'Notifications',
- 'OAuth Apps',
'Pages',
+ 'Performance',
'Permissions',
'Policies',
'Policy',
+ 'Powershell',
+ 'Pre-receive hooks',
+ 'Privacy',
'Profile',
'Profiles',
+ 'Project management',
'Projects',
+ 'Publishing',
'Pull requests',
+ 'Python',
'Receipts',
'Repositories',
+ 'REST',
+ 'Ruby',
+ 'SARIF',
+ 'Secret scanning',
+ 'Secret store',
+ 'Security advisories',
+ 'Security overview',
+ 'Security policies',
+ 'Security updates',
'Security',
- 'Spending limits',
- 'Support',
'Set up',
+ 'Spending limits',
+ 'Sponsors payments',
+ 'Sponsors profile',
+ 'Sponsors',
'SSH',
'SSO',
+ 'Storage',
+ 'Support',
+ 'Swift',
'Teams',
+ 'Travis CI',
'Trials',
'Troubleshooting',
'Upgrades',
+ 'User account',
'Usernames',
+ 'Version updates',
'Visual Studio Code',
- 'Xamarin',
- 'Xamarin.iOS',
+ 'Vulnerabilities',
+ 'Webhooks',
+ 'Workflows',
'Xamarin.Android',
+ 'Xamarin.iOS',
+ 'Xamarin',
'Xcode'
]
diff --git a/data/release-notes/2-20/0.yml b/data/release-notes/enterprise-server/2-20/0.yml
similarity index 100%
rename from data/release-notes/2-20/0.yml
rename to data/release-notes/enterprise-server/2-20/0.yml
diff --git a/data/release-notes/2-20/1.yml b/data/release-notes/enterprise-server/2-20/1.yml
similarity index 100%
rename from data/release-notes/2-20/1.yml
rename to data/release-notes/enterprise-server/2-20/1.yml
diff --git a/data/release-notes/2-20/10.yml b/data/release-notes/enterprise-server/2-20/10.yml
similarity index 100%
rename from data/release-notes/2-20/10.yml
rename to data/release-notes/enterprise-server/2-20/10.yml
diff --git a/data/release-notes/2-20/11.yml b/data/release-notes/enterprise-server/2-20/11.yml
similarity index 100%
rename from data/release-notes/2-20/11.yml
rename to data/release-notes/enterprise-server/2-20/11.yml
diff --git a/data/release-notes/2-20/12.yml b/data/release-notes/enterprise-server/2-20/12.yml
similarity index 100%
rename from data/release-notes/2-20/12.yml
rename to data/release-notes/enterprise-server/2-20/12.yml
diff --git a/data/release-notes/2-20/13.yml b/data/release-notes/enterprise-server/2-20/13.yml
similarity index 100%
rename from data/release-notes/2-20/13.yml
rename to data/release-notes/enterprise-server/2-20/13.yml
diff --git a/data/release-notes/2-20/14.yml b/data/release-notes/enterprise-server/2-20/14.yml
similarity index 100%
rename from data/release-notes/2-20/14.yml
rename to data/release-notes/enterprise-server/2-20/14.yml
diff --git a/data/release-notes/2-20/15.yml b/data/release-notes/enterprise-server/2-20/15.yml
similarity index 100%
rename from data/release-notes/2-20/15.yml
rename to data/release-notes/enterprise-server/2-20/15.yml
diff --git a/data/release-notes/2-20/16.yml b/data/release-notes/enterprise-server/2-20/16.yml
similarity index 100%
rename from data/release-notes/2-20/16.yml
rename to data/release-notes/enterprise-server/2-20/16.yml
diff --git a/data/release-notes/2-20/17.yml b/data/release-notes/enterprise-server/2-20/17.yml
similarity index 100%
rename from data/release-notes/2-20/17.yml
rename to data/release-notes/enterprise-server/2-20/17.yml
diff --git a/data/release-notes/2-20/18.yml b/data/release-notes/enterprise-server/2-20/18.yml
similarity index 100%
rename from data/release-notes/2-20/18.yml
rename to data/release-notes/enterprise-server/2-20/18.yml
diff --git a/data/release-notes/2-20/19.yml b/data/release-notes/enterprise-server/2-20/19.yml
similarity index 100%
rename from data/release-notes/2-20/19.yml
rename to data/release-notes/enterprise-server/2-20/19.yml
diff --git a/data/release-notes/2-20/2.yml b/data/release-notes/enterprise-server/2-20/2.yml
similarity index 100%
rename from data/release-notes/2-20/2.yml
rename to data/release-notes/enterprise-server/2-20/2.yml
diff --git a/data/release-notes/2-20/20.yml b/data/release-notes/enterprise-server/2-20/20.yml
similarity index 100%
rename from data/release-notes/2-20/20.yml
rename to data/release-notes/enterprise-server/2-20/20.yml
diff --git a/data/release-notes/2-20/21.yml b/data/release-notes/enterprise-server/2-20/21.yml
similarity index 100%
rename from data/release-notes/2-20/21.yml
rename to data/release-notes/enterprise-server/2-20/21.yml
diff --git a/data/release-notes/2-20/22.yml b/data/release-notes/enterprise-server/2-20/22.yml
similarity index 100%
rename from data/release-notes/2-20/22.yml
rename to data/release-notes/enterprise-server/2-20/22.yml
diff --git a/data/release-notes/2-20/23.yml b/data/release-notes/enterprise-server/2-20/23.yml
similarity index 100%
rename from data/release-notes/2-20/23.yml
rename to data/release-notes/enterprise-server/2-20/23.yml
diff --git a/data/release-notes/2-20/24.yml b/data/release-notes/enterprise-server/2-20/24.yml
similarity index 100%
rename from data/release-notes/2-20/24.yml
rename to data/release-notes/enterprise-server/2-20/24.yml
diff --git a/data/release-notes/2-20/3.yml b/data/release-notes/enterprise-server/2-20/3.yml
similarity index 100%
rename from data/release-notes/2-20/3.yml
rename to data/release-notes/enterprise-server/2-20/3.yml
diff --git a/data/release-notes/2-20/4.yml b/data/release-notes/enterprise-server/2-20/4.yml
similarity index 100%
rename from data/release-notes/2-20/4.yml
rename to data/release-notes/enterprise-server/2-20/4.yml
diff --git a/data/release-notes/2-20/5.yml b/data/release-notes/enterprise-server/2-20/5.yml
similarity index 100%
rename from data/release-notes/2-20/5.yml
rename to data/release-notes/enterprise-server/2-20/5.yml
diff --git a/data/release-notes/2-20/6.yml b/data/release-notes/enterprise-server/2-20/6.yml
similarity index 100%
rename from data/release-notes/2-20/6.yml
rename to data/release-notes/enterprise-server/2-20/6.yml
diff --git a/data/release-notes/2-20/7.yml b/data/release-notes/enterprise-server/2-20/7.yml
similarity index 100%
rename from data/release-notes/2-20/7.yml
rename to data/release-notes/enterprise-server/2-20/7.yml
diff --git a/data/release-notes/2-20/8.yml b/data/release-notes/enterprise-server/2-20/8.yml
similarity index 100%
rename from data/release-notes/2-20/8.yml
rename to data/release-notes/enterprise-server/2-20/8.yml
diff --git a/data/release-notes/2-20/9.yml b/data/release-notes/enterprise-server/2-20/9.yml
similarity index 100%
rename from data/release-notes/2-20/9.yml
rename to data/release-notes/enterprise-server/2-20/9.yml
diff --git a/data/release-notes/2-21/0.yml b/data/release-notes/enterprise-server/2-21/0.yml
similarity index 100%
rename from data/release-notes/2-21/0.yml
rename to data/release-notes/enterprise-server/2-21/0.yml
diff --git a/data/release-notes/2-21/1.yml b/data/release-notes/enterprise-server/2-21/1.yml
similarity index 100%
rename from data/release-notes/2-21/1.yml
rename to data/release-notes/enterprise-server/2-21/1.yml
diff --git a/data/release-notes/2-21/10.yml b/data/release-notes/enterprise-server/2-21/10.yml
similarity index 100%
rename from data/release-notes/2-21/10.yml
rename to data/release-notes/enterprise-server/2-21/10.yml
diff --git a/data/release-notes/2-21/11.yml b/data/release-notes/enterprise-server/2-21/11.yml
similarity index 100%
rename from data/release-notes/2-21/11.yml
rename to data/release-notes/enterprise-server/2-21/11.yml
diff --git a/data/release-notes/2-21/12.yml b/data/release-notes/enterprise-server/2-21/12.yml
similarity index 100%
rename from data/release-notes/2-21/12.yml
rename to data/release-notes/enterprise-server/2-21/12.yml
diff --git a/data/release-notes/2-21/13.yml b/data/release-notes/enterprise-server/2-21/13.yml
similarity index 100%
rename from data/release-notes/2-21/13.yml
rename to data/release-notes/enterprise-server/2-21/13.yml
diff --git a/data/release-notes/2-21/14.yml b/data/release-notes/enterprise-server/2-21/14.yml
similarity index 100%
rename from data/release-notes/2-21/14.yml
rename to data/release-notes/enterprise-server/2-21/14.yml
diff --git a/data/release-notes/2-21/15.yml b/data/release-notes/enterprise-server/2-21/15.yml
similarity index 100%
rename from data/release-notes/2-21/15.yml
rename to data/release-notes/enterprise-server/2-21/15.yml
diff --git a/data/release-notes/2-21/16.yml b/data/release-notes/enterprise-server/2-21/16.yml
similarity index 100%
rename from data/release-notes/2-21/16.yml
rename to data/release-notes/enterprise-server/2-21/16.yml
diff --git a/data/release-notes/2-21/17.yml b/data/release-notes/enterprise-server/2-21/17.yml
similarity index 100%
rename from data/release-notes/2-21/17.yml
rename to data/release-notes/enterprise-server/2-21/17.yml
diff --git a/data/release-notes/2-21/18.yml b/data/release-notes/enterprise-server/2-21/18.yml
similarity index 100%
rename from data/release-notes/2-21/18.yml
rename to data/release-notes/enterprise-server/2-21/18.yml
diff --git a/data/release-notes/2-21/19.yml b/data/release-notes/enterprise-server/2-21/19.yml
similarity index 100%
rename from data/release-notes/2-21/19.yml
rename to data/release-notes/enterprise-server/2-21/19.yml
diff --git a/data/release-notes/2-21/2.yml b/data/release-notes/enterprise-server/2-21/2.yml
similarity index 100%
rename from data/release-notes/2-21/2.yml
rename to data/release-notes/enterprise-server/2-21/2.yml
diff --git a/data/release-notes/2-21/20.yml b/data/release-notes/enterprise-server/2-21/20.yml
similarity index 100%
rename from data/release-notes/2-21/20.yml
rename to data/release-notes/enterprise-server/2-21/20.yml
diff --git a/data/release-notes/2-21/21.yml b/data/release-notes/enterprise-server/2-21/21.yml
similarity index 100%
rename from data/release-notes/2-21/21.yml
rename to data/release-notes/enterprise-server/2-21/21.yml
diff --git a/data/release-notes/2-21/22.yml b/data/release-notes/enterprise-server/2-21/22.yml
similarity index 100%
rename from data/release-notes/2-21/22.yml
rename to data/release-notes/enterprise-server/2-21/22.yml
diff --git a/data/release-notes/2-21/3.yml b/data/release-notes/enterprise-server/2-21/3.yml
similarity index 100%
rename from data/release-notes/2-21/3.yml
rename to data/release-notes/enterprise-server/2-21/3.yml
diff --git a/data/release-notes/2-21/4.yml b/data/release-notes/enterprise-server/2-21/4.yml
similarity index 100%
rename from data/release-notes/2-21/4.yml
rename to data/release-notes/enterprise-server/2-21/4.yml
diff --git a/data/release-notes/2-21/5.yml b/data/release-notes/enterprise-server/2-21/5.yml
similarity index 100%
rename from data/release-notes/2-21/5.yml
rename to data/release-notes/enterprise-server/2-21/5.yml
diff --git a/data/release-notes/2-21/6.yml b/data/release-notes/enterprise-server/2-21/6.yml
similarity index 100%
rename from data/release-notes/2-21/6.yml
rename to data/release-notes/enterprise-server/2-21/6.yml
diff --git a/data/release-notes/2-21/7.yml b/data/release-notes/enterprise-server/2-21/7.yml
similarity index 100%
rename from data/release-notes/2-21/7.yml
rename to data/release-notes/enterprise-server/2-21/7.yml
diff --git a/data/release-notes/2-21/8.yml b/data/release-notes/enterprise-server/2-21/8.yml
similarity index 100%
rename from data/release-notes/2-21/8.yml
rename to data/release-notes/enterprise-server/2-21/8.yml
diff --git a/data/release-notes/2-21/9.yml b/data/release-notes/enterprise-server/2-21/9.yml
similarity index 100%
rename from data/release-notes/2-21/9.yml
rename to data/release-notes/enterprise-server/2-21/9.yml
diff --git a/data/release-notes/2-22/0.yml b/data/release-notes/enterprise-server/2-22/0.yml
similarity index 100%
rename from data/release-notes/2-22/0.yml
rename to data/release-notes/enterprise-server/2-22/0.yml
diff --git a/data/release-notes/2-22/1.yml b/data/release-notes/enterprise-server/2-22/1.yml
similarity index 100%
rename from data/release-notes/2-22/1.yml
rename to data/release-notes/enterprise-server/2-22/1.yml
diff --git a/data/release-notes/2-22/10.yml b/data/release-notes/enterprise-server/2-22/10.yml
similarity index 100%
rename from data/release-notes/2-22/10.yml
rename to data/release-notes/enterprise-server/2-22/10.yml
diff --git a/data/release-notes/2-22/11.yml b/data/release-notes/enterprise-server/2-22/11.yml
similarity index 100%
rename from data/release-notes/2-22/11.yml
rename to data/release-notes/enterprise-server/2-22/11.yml
diff --git a/data/release-notes/2-22/12.yml b/data/release-notes/enterprise-server/2-22/12.yml
similarity index 100%
rename from data/release-notes/2-22/12.yml
rename to data/release-notes/enterprise-server/2-22/12.yml
diff --git a/data/release-notes/2-22/13.yml b/data/release-notes/enterprise-server/2-22/13.yml
similarity index 100%
rename from data/release-notes/2-22/13.yml
rename to data/release-notes/enterprise-server/2-22/13.yml
diff --git a/data/release-notes/2-22/14.yml b/data/release-notes/enterprise-server/2-22/14.yml
similarity index 100%
rename from data/release-notes/2-22/14.yml
rename to data/release-notes/enterprise-server/2-22/14.yml
diff --git a/data/release-notes/2-22/2.yml b/data/release-notes/enterprise-server/2-22/2.yml
similarity index 100%
rename from data/release-notes/2-22/2.yml
rename to data/release-notes/enterprise-server/2-22/2.yml
diff --git a/data/release-notes/2-22/3.yml b/data/release-notes/enterprise-server/2-22/3.yml
similarity index 100%
rename from data/release-notes/2-22/3.yml
rename to data/release-notes/enterprise-server/2-22/3.yml
diff --git a/data/release-notes/2-22/4.yml b/data/release-notes/enterprise-server/2-22/4.yml
similarity index 100%
rename from data/release-notes/2-22/4.yml
rename to data/release-notes/enterprise-server/2-22/4.yml
diff --git a/data/release-notes/2-22/5.yml b/data/release-notes/enterprise-server/2-22/5.yml
similarity index 100%
rename from data/release-notes/2-22/5.yml
rename to data/release-notes/enterprise-server/2-22/5.yml
diff --git a/data/release-notes/2-22/6.yml b/data/release-notes/enterprise-server/2-22/6.yml
similarity index 100%
rename from data/release-notes/2-22/6.yml
rename to data/release-notes/enterprise-server/2-22/6.yml
diff --git a/data/release-notes/2-22/7.yml b/data/release-notes/enterprise-server/2-22/7.yml
similarity index 100%
rename from data/release-notes/2-22/7.yml
rename to data/release-notes/enterprise-server/2-22/7.yml
diff --git a/data/release-notes/2-22/8.yml b/data/release-notes/enterprise-server/2-22/8.yml
similarity index 100%
rename from data/release-notes/2-22/8.yml
rename to data/release-notes/enterprise-server/2-22/8.yml
diff --git a/data/release-notes/2-22/9.yml b/data/release-notes/enterprise-server/2-22/9.yml
similarity index 100%
rename from data/release-notes/2-22/9.yml
rename to data/release-notes/enterprise-server/2-22/9.yml
diff --git a/data/release-notes/3-0/0-rc1.yml b/data/release-notes/enterprise-server/3-0/0-rc1.yml
similarity index 100%
rename from data/release-notes/3-0/0-rc1.yml
rename to data/release-notes/enterprise-server/3-0/0-rc1.yml
diff --git a/data/release-notes/3-0/0-rc2.yml b/data/release-notes/enterprise-server/3-0/0-rc2.yml
similarity index 100%
rename from data/release-notes/3-0/0-rc2.yml
rename to data/release-notes/enterprise-server/3-0/0-rc2.yml
diff --git a/data/release-notes/3-0/0.yml b/data/release-notes/enterprise-server/3-0/0.yml
similarity index 100%
rename from data/release-notes/3-0/0.yml
rename to data/release-notes/enterprise-server/3-0/0.yml
diff --git a/data/release-notes/3-0/1.yml b/data/release-notes/enterprise-server/3-0/1.yml
similarity index 100%
rename from data/release-notes/3-0/1.yml
rename to data/release-notes/enterprise-server/3-0/1.yml
diff --git a/data/release-notes/3-0/2.yml b/data/release-notes/enterprise-server/3-0/2.yml
similarity index 100%
rename from data/release-notes/3-0/2.yml
rename to data/release-notes/enterprise-server/3-0/2.yml
diff --git a/data/release-notes/3-0/3.yml b/data/release-notes/enterprise-server/3-0/3.yml
similarity index 100%
rename from data/release-notes/3-0/3.yml
rename to data/release-notes/enterprise-server/3-0/3.yml
diff --git a/data/release-notes/3-0/4.yml b/data/release-notes/enterprise-server/3-0/4.yml
similarity index 100%
rename from data/release-notes/3-0/4.yml
rename to data/release-notes/enterprise-server/3-0/4.yml
diff --git a/data/release-notes/3-0/5.yml b/data/release-notes/enterprise-server/3-0/5.yml
similarity index 100%
rename from data/release-notes/3-0/5.yml
rename to data/release-notes/enterprise-server/3-0/5.yml
diff --git a/data/release-notes/3-0/6.yml b/data/release-notes/enterprise-server/3-0/6.yml
similarity index 100%
rename from data/release-notes/3-0/6.yml
rename to data/release-notes/enterprise-server/3-0/6.yml
diff --git a/data/release-notes/3-0/7.yml b/data/release-notes/enterprise-server/3-0/7.yml
similarity index 100%
rename from data/release-notes/3-0/7.yml
rename to data/release-notes/enterprise-server/3-0/7.yml
diff --git a/data/release-notes/3-0/8.yml b/data/release-notes/enterprise-server/3-0/8.yml
similarity index 100%
rename from data/release-notes/3-0/8.yml
rename to data/release-notes/enterprise-server/3-0/8.yml
diff --git a/data/release-notes/3-1/0-rc1.yml b/data/release-notes/enterprise-server/3-1/0-rc1.yml
similarity index 95%
rename from data/release-notes/3-1/0-rc1.yml
rename to data/release-notes/enterprise-server/3-1/0-rc1.yml
index 3d06e0e705..5b28c70d8d 100644
--- a/data/release-notes/3-1/0-rc1.yml
+++ b/data/release-notes/enterprise-server/3-1/0-rc1.yml
@@ -18,6 +18,11 @@ sections:
Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+ - heading: GitHub Advanced Security Code Scanning
+ notes:
+ - |
+ [{% data variables.product.prodname_GH_advanced_security %} code scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Organizations who have purchased {% data variables.product.prodname_GH_advanced_security %} can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.1/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)."
+
- heading: GitHub Advanced Security billing improvements
notes:
- |
diff --git a/data/release-notes/enterprise-server/README.md b/data/release-notes/enterprise-server/README.md
new file mode 100644
index 0000000000..5a488316c8
--- /dev/null
+++ b/data/release-notes/enterprise-server/README.md
@@ -0,0 +1,37 @@
+# Release notes for GitHub Enterprise Server
+
+Rendered here: https://docs.github.com/en/enterprise-server@latest/admin/release-notes
+
+## How it works
+
+### Placeholder content file
+
+A content file exists in `content/admin/release-notes.md`. It has a special frontmatter property `layout: release-notes` and no Markdown content. The source of the release notes comes from YAML data.
+
+### YAML source
+
+The source data for the release notes lives in this directory (`data/release-notes/enterprise-server`).
+
+The directories are named by GHES release number (with a hyphen instead of a period).
+
+The YAML files in each directory are named by patch number. Some patch filenames may end with `-rc.yml`, which means it's a release candidate. A release candidate file also requires `release_candidate: true` in the YAML data.
+
+Release notes of deprecated GHES versions (see `lib/enterprise-server-releases.js`) are **not** removed from the site and will always be displayed alongside currently supported versions.
+
+Note that patch files can be deprecated individually (i.e., hidden on the docs site) by an optional `deprecated: true` property.
+
+### Middleware processing
+
+The YAML data is processed and sorted by `middleware/contextualizers/release-notes.js` and added to the `context` object.
+
+### Layouts
+
+The `context` object data is rendered by `layouts/release-notes.html` and `includes/enterprise-server-release-notes.html`.
+
+The release notes page has a custom design with CSS in `stylesheets/release-notes.scss` and client-side JavaScript in `javascripts/release-notes.js`.
+
+### Schema
+
+The schema that validates the YAML data lives in `tests/helpers/schemas/ghes-release-notes-schema.js`. See the schema file to find out the required and optional properties.
+
+The schema is exercised by a test in `tests/linting/lint-files.js`. The test will fail if the data does not pass validation.
diff --git a/data/release-notes/github-ae/2021-03/2021-03-03.yml b/data/release-notes/github-ae/2021-03/2021-03-03.yml
new file mode 100644
index 0000000000..7185cd78c4
--- /dev/null
+++ b/data/release-notes/github-ae/2021-03/2021-03-03.yml
@@ -0,0 +1,83 @@
+date: '2021-03-03'
+friendlyDate: 'March 3, 2021'
+title: 'Week of March 3, 2021'
+currentWeek: false
+sections:
+ features:
+ - heading: 'GitHub Actions beta'
+ notes:
+ - |
+ [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
+
+ {% data variables.product.prodname_actions %} on {% data variables.product.product_name %} uses a new [{% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners), only available for {% data variables.product.product_name %}, that enables you to customize the size, image, and networking configuration of the runners. These runners are a finished-service CI compute environment with auto-scaling and management, fully managed by {% data variables.product.company_short %}. During the beta, the use {% data variables.actions.hosted_runner %}s is free of charge. For more information, see "[Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)."
+
+ Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.product.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log.
+ - heading: 'GitHub Packages beta'
+ notes:
+ - |
+ [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with {% data variables.product.prodname_actions %}, APIs, and webhooks. Create an [end-to-end DevOps workflow](/github-ae@latest/packages/quickstart) that includes your code, continuous integration, and deployment solutions. During this beta, {% data variables.product.prodname_registry %} is offered free of charge to {% data variables.product.product_name %} customers.
+ - heading: 'GitHub Advanced Security beta'
+ notes:
+ - |
+ {% data variables.product.prodname_GH_advanced_security %} is available in beta and includes both code scanning and secret scanning. During this beta, {% data variables.product.prodname_GH_advanced_security %} features are being offered free of charge to {% data variables.product.product_name %} customers. Repository and organization administrators can opt-in to use {% data variables.product.prodname_GH_advanced_security %} in the Security and Analysis tab under settings.
+
+ Learn more about {% data variables.product.prodname_GH_advanced_security %} [code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) and [secret scanning](/github/administering-a-repository/about-secret-scanning) on {% data variables.product.prodname_ghe_managed %}.
+
+ - heading: Manage teams from your identity provider (IdP)
+ notes:
+ - |
+ Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group.
+
+ - heading: IP allow lists beta
+ notes:
+ - |
+ [{% data variables.product.company_short %} IP allow lists](/admin/configuration/restricting-network-traffic-to-your-enterprise) provide the ability to filter traffic from administrator-specified IP ranges, defined by CIDR notation. The allow list is defined at the enterprise or organization account level in Security > Settings. All traffic that attempts to reach resources within the enterprise account and organizations are filtered by the IP allow lists. This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the GHAE tenant.
+
+ changes:
+ - heading: Developer Changes
+ notes:
+ - |
+ [Organization owners can now disable publication](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites.
+ - Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).
+ - When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`.
+ - You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory.
+ - It's now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#".
+
+ - heading: Administration changes
+ notes:
+ - Enterprise owners can now publish a mandatory message. The message is shown to all users and they must acknowledge it. This can be used to display important information, terms of service or policies.
+ - The {% data variables.product.prodname_github_app%} single file path permission can now [support up to ten files](/developers/apps/creating-a-github-app-using-url-parameters).
+ - When configuring a {% data variables.product.prodname_github_app%}, the authorization callback URL is a required field. Now we will permit the integrator to specify multiple callback URLs. {% data variables.product.product_name %} denies authorization if the callback URL from the request is not listed.
+ - A [new API endpoint](/rest/reference/apps#create-a-scoped-access-token) enables the exchange of a user to server token for a user to server token scoped to specific repositories.
+ - Events are now logged in the audit log on [promoting a team member to be a team maintainer and on demoting a team maintainer to be a team member](/admin/user-management/audited-actions#teams).
+ - The [OAuth device authorization flow](/developers/apps/authorizing-oauth-apps#device-flow) is now supported. This allows any CLI client or developer tool to authenticate using a secondary system.
+ - A user can no longer delete their account if SCIM provisioning is enabled.
+
+ - heading: Default branch renaming
+ notes:
+ - |
+ Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own.
+
+ Existing repositories are unaffected by these settings, and their default branch name will not be changed.
+
+ This change is one of many changes {% data variables.product.company_short %} is making to support projects and maintainers that want to rename their default branch. To learn more, see [github/renaming](https://github.com/github/renaming).
+
+ bugs:
+ - heading: Bug fixes
+ notes:
+ - Users can no longer set a backup email address on their profile. Their email address is set through the IdP only.
+ - You can no longer enable two-factor authentication after configuring authentication through your IdP.
+ - |
+ {% data variables.product.product_name %} can now connect to Azure Boards.
+ - Version headers were missing from the APIs, and have now been set to "GitHub AE."
+ - Links to documentation have been fixed.
+ - Configuration of audit log forwarding within the enterprise's settings was failing.
+ - Navigating to gists could result in a 500 error.
+ - The Support email or URL was failing to save. It now saves after a period of a few minutes.
+ - Organization level pull request templates were not being applied to all pull requests in the organization.
+
+ known_issues:
+ - heading: Known issues
+ notes:
+ - Geographic location data is not shown in the audit log. Location information can otherwise be discerned from the IP address associated with each event.
+ - The link to {% data variables.product.prodname_registry %} from a repository page shows an incorrect search page when that repository does not have any packages.
diff --git a/data/release-notes/github-ae/README.md b/data/release-notes/github-ae/README.md
new file mode 100644
index 0000000000..b20276bebd
--- /dev/null
+++ b/data/release-notes/github-ae/README.md
@@ -0,0 +1,35 @@
+# Release notes for GitHub AE
+
+Rendered here: https://docs.github.com/en/github-ae@latest/admin/release-notes
+
+## How it works
+
+### Placeholder content file
+
+A content file exists in `content/admin/release-notes.md`. It has a special frontmatter property `layout: release-notes` and no Markdown content. The source of the release notes comes from YAML data.
+
+### YAML source
+
+The source data for the release notes lives in this directory (`data/release-notes/github-ae`).
+
+The directories are named by month. The YAML files are named by the data of a weekly release.
+
+A boolean property called `currentWeek` must be set in each YAML file. No more than one file at a time can have this property set to true.
+
+Note that patch files can be deprecated individually (i.e., hidden on the docs site) by an optional `deprecated: true` property.
+
+### Middleware processing
+
+The YAML data is processed and sorted by `middleware/contextualizers/release-notes.js` and added to the `context` object.
+
+### Layouts
+
+The `context` object data is rendered by `layouts/release-notes.html` and `includes/github-ae-release-notes.html`.
+
+The release notes page has a custom design with CSS in `stylesheets/release-notes.scss` and client-side JavaScript in `javascripts/release-notes.js`.
+
+### Schema
+
+The schema that validates the YAML data lives in `tests/helpers/schemas/ghae-release-notes-schema.js`. See the schema file to find out the required and optional properties.
+
+The schema is exercised by a test in `tests/linting/lint-files.js`. The test will fail if the data does not pass validation.
diff --git a/data/reusables/enterprise_migrations/locking-repositories.md b/data/reusables/enterprise_migrations/locking-repositories.md
index f44ff52c94..ea0ecd6bcf 100644
--- a/data/reusables/enterprise_migrations/locking-repositories.md
+++ b/data/reusables/enterprise_migrations/locking-repositories.md
@@ -1,6 +1,6 @@
{% tip %}
-**Note:** Locking a repository prevents users from pushing to the repository or modifying a repository's resources, like issues, labels, milestones, wikis, and comments. New teams and collaborators can't be associated with a locked repository.
+**Note:** Locking a repository prevents all read or write access to the repository. You cannot associate new teams or collaborators with a locked repository.
-If you're performing a trial run, you don't need to lock repositories. Otherwise, it's highly recommended. For more information, see "[About Migrations](/enterprise/admin/migrations/about-migrations#types-of-migrations)."
+If you're performing a trial run, you do not need to lock the repository. When you migrate data from a repository that's in use, {% data variables.product.company_short %} strongly recommends locking the repository. For more information, see "[About Migrations](/enterprise/admin/migrations/about-migrations#types-of-migrations)."
{% endtip %}
diff --git a/data/reusables/files/choose_pull_request.md b/data/reusables/files/choose_pull_request.md
new file mode 100644
index 0000000000..0f44609362
--- /dev/null
+++ b/data/reusables/files/choose_pull_request.md
@@ -0,0 +1,2 @@
+1. Create a pull request for your proposed changes.
+2. In the "Pull Requests" list, click the pull request you would like to merge.
diff --git a/data/reusables/files/confirm_merge.md b/data/reusables/files/confirm_merge.md
new file mode 100644
index 0000000000..44576e1a37
--- /dev/null
+++ b/data/reusables/files/confirm_merge.md
@@ -0,0 +1 @@
+1. Click **Confirm merge**.
diff --git a/data/reusables/files/delete_branch.md b/data/reusables/files/delete_branch.md
new file mode 100644
index 0000000000..651f7eae61
--- /dev/null
+++ b/data/reusables/files/delete_branch.md
@@ -0,0 +1 @@
+1. Optionally, delete the branch. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)."
diff --git a/data/reusables/files/merge_pull_request.md b/data/reusables/files/merge_pull_request.md
new file mode 100644
index 0000000000..21365cb488
--- /dev/null
+++ b/data/reusables/files/merge_pull_request.md
@@ -0,0 +1 @@
+1. Click **Merge pull request**. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)."
diff --git a/data/reusables/files/write_commit_message_pull_request.md b/data/reusables/files/write_commit_message_pull_request.md
new file mode 100644
index 0000000000..ba5c7925d7
--- /dev/null
+++ b/data/reusables/files/write_commit_message_pull_request.md
@@ -0,0 +1,2 @@
+1. If prompted, type a commit message, or accept the default message.
+ 
diff --git a/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
index 6391060874..2ebe7f6417 100644
--- a/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
+++ b/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
@@ -1,4 +1,4 @@
-1. In the upper-right corner of any page, click your profile photo, then click **{% data variables.product.prodname_sponsors %}**.
+1. In the upper-right corner of any page, click your profile photo, then click **Your sponsors**.

2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**.

diff --git a/data/reusables/sponsors/tier-details.md b/data/reusables/sponsors/tier-details.md
index 78c40c1054..2aed4e826b 100644
--- a/data/reusables/sponsors/tier-details.md
+++ b/data/reusables/sponsors/tier-details.md
@@ -1,3 +1,10 @@
-You can create up to ten sponsorship tiers for sponsors to choose from. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time).
+You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time).
-Once you have published a tier, you can't edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires.
+You can customize the rewards for each tier. For example, rewards for a tier could include:
+- Early access to new versions
+- Logo or name in README
+- Access to a private repository
+- Weekly newsletter updates
+- Other rewards your sponsors would enjoy ✨
+
+Once you have published a tier, you cannot edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires.
diff --git a/data/reusables/webhooks/secret.md b/data/reusables/webhooks/secret.md
index 95f3a341ca..a92e5fca87 100644
--- a/data/reusables/webhooks/secret.md
+++ b/data/reusables/webhooks/secret.md
@@ -1 +1 @@
-Setting a webhook secret allows you to ensure that `POST` requests sent to the payload URL are from {% data variables.product.product_name %}. When you set a secret, you'll receive the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature` and `X-Hub-Signature-256` headers{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` header{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` header{% endif %} in the webhook `POST` request. For more information on how to use a secret with a signature header to secure your webhook payloads, see "[Securing your webhooks](/webhooks/securing/)."
+Setting a webhook secret allows you to ensure that `POST` requests sent to the payload URL are from {% data variables.product.product_name %}. When you set a secret, you'll receive the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`X-Hub-Signature` and `X-Hub-Signature-256` headers{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` header{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` header{% endif %} in the webhook `POST` request. For more information on how to use a secret with a signature header to secure your webhook payloads, see "[Securing your webhooks](/webhooks/securing/)."
diff --git a/data/ui.yml b/data/ui.yml
index 261ade0760..f2bb008dea 100644
--- a/data/ui.yml
+++ b/data/ui.yml
@@ -18,10 +18,14 @@ header:
please visit our
English documentation.
early_access: 📣 Please do not share this URL publicly. This page contains content about an early access feature.
- ghes_release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes.
- ghes_release_notes_upgrade_patch_only: 📣 This is not the latest patch release of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}
- ghes_release_notes_upgrade_release_only: 📣 This is not the latest release of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}
- ghes_release_notes_upgrade_patch_and_release: 📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}
+ release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes.
+ # GHES release notes
+ ghes_release_notes_upgrade_patch_only: 📣 This is not the latest patch release of Enterprise Server. {% data ui.header.notices.release_notes_use_latest %}
+ ghes_release_notes_upgrade_release_only: 📣 This is not the latest release of Enterprise Server. {% data ui.header.notices.release_notes_use_latest %}
+ ghes_release_notes_upgrade_patch_and_release: 📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. {% data ui.header.notices.release_notes_use_latest %}
+release_notes:
+ banner_text_current: These changes will roll out over the next one week.
+ banner_text_past: These changes rolled out to enterprises during the week of
search:
need_help: Need help?
placeholder: Search topics, products...
diff --git a/includes/enterprise-server-release-notes.html b/includes/enterprise-server-release-notes.html
new file mode 100644
index 0000000000..88806054b0
--- /dev/null
+++ b/includes/enterprise-server-release-notes.html
@@ -0,0 +1,156 @@
+{% assign product = siteTree[currentLanguage][currentVersion].products[currentProduct] %}
+{% assign currentVersionObject = allVersions[currentVersion] %}
+
+
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.18/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.18/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.18/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@2.18/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.18/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.18/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.18/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.18/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@2.18/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.18/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.19/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.19/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.19/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@2.19/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.19/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.19/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.19/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.19/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@2.19/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.19/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.20/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.20/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.20/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@2.20/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.20/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.20/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.20/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.20/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@2.20/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.20/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.21/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.21/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.21/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@2.21/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.21/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.21/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.21/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.21/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@2.21/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.21/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.22/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.22/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.22/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@2.22/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@2.22/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@2.22/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@2.22/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@2.22/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@3.0/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@3.0/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@3.0/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@3.0/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@3.1/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/enterprise-server@3.1/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/enterprise-server@3.1/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/enterprise-server@3.1/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
+ }
+ ],
+ "summary": "Create a content attachment",
+ "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/github-ae@latest/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
+ "tags": [
+ "apps"
+ ],
+ "operationId": "apps/create-content-attachment",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/github-ae@latest/rest/reference/apps#create-a-content-attachment"
+ },
+ "requestBody": {
+ "content": {
+ "application/json": {
+ "schema": {
+ "properties": {
+ "title": {
+ "description": "
Required. The title of the attachment
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ "body": {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "title",
+ "body"
+ ],
+ "type": "object"
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+ {
+ "required": true,
+ "name": "corsair",
+ "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
+ "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
+ "example": "Title of the attachment",
+ "type": "string",
+ "maxLength": 1024,
+ "name": "title",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The title of the attachment",
+ "childParamsGroups": []
+ },
+ {
+ "description": "
Required. The body of the attachment
",
+ "example": "Body of the attachment",
+ "type": "string",
+ "maxLength": 262144,
+ "name": "body",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "The body of the attachment",
+ "childParamsGroups": []
+ }
+ ],
+ "responses": [
+ {
+ "httpStatusCode": "200",
+ "httpStatusMessage": "OK",
+ "description": "Response",
+ "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n
"
- }
- ],
- "summary": "Create a content attachment",
- "description": "Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the `id` and `repository` `full_name` of the content reference from the [`content_reference` event](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#content_reference) to create an attachment.\n\nThe app must create a content attachment within six hours of the content reference URL being posted. See \"[Using content attachments](https://docs.github.com/github-ae@latest/apps/using-content-attachments/)\" for details about content attachments.\n\nYou must use an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.",
- "tags": [
- "apps"
- ],
- "operationId": "apps/create-content-attachment",
- "externalDocs": {
- "description": "API method documentation",
- "url": "https://docs.github.com/github-ae@latest/rest/reference/apps#create-a-content-attachment"
- },
- "requestBody": {
- "content": {
- "application/json": {
- "schema": {
- "properties": {
- "title": {
- "description": "
Required. The title of the attachment
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- "body": {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- },
- "required": [
- "title",
- "body"
- ],
- "type": "object"
- }
- }
- }
- },
- "x-github": {
- "githubCloudOnly": false,
- "enabledForGitHubApps": true,
- "previews": [
- {
- "required": true,
- "name": "corsair",
- "note": "To access the Content Attachments API during the preview period, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.corsair-preview+json\n```",
- "html": "
To access the Content Attachments API during the preview period, you must provide a custom media type in the Accept header:
Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repositoryfull_name of the content reference from the content_reference event to create an attachment.
\n
The app must create a content attachment within six hours of the content reference URL being posted. See \"Using content attachments\" for details about content attachments.
",
- "example": "Title of the attachment",
- "type": "string",
- "maxLength": 1024,
- "name": "title",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The title of the attachment",
- "childParamsGroups": []
- },
- {
- "description": "
Required. The body of the attachment
",
- "example": "Body of the attachment",
- "type": "string",
- "maxLength": 262144,
- "name": "body",
- "in": "body",
- "rawType": "string",
- "rawDescription": "The body of the attachment",
- "childParamsGroups": []
- }
- ],
- "responses": [
- {
- "httpStatusCode": "200",
- "httpStatusMessage": "OK",
- "description": "Response",
- "payload": "
{\n \"id\": 101,\n \"title\": \"[A-1234] Error found in core/models.py file'\",\n \"body\": \"You have used an email that already exists for the user_email_uniq field.\\n ## DETAILS:\\n\\nThe (email)=(Octocat@github.com) already exists.\\n\\n The error was found in core/models.py in get_or_create_user at line 62.\\n\\n self.save()\"\n}\n