Merge branch 'main' into patch-2

Author: theking2

content/admin/managing-your-enterprise-account/configuring-user-display-names-for-your-enterprise.md

@@ -3,7 +3,7 @@ title: 'Configuring user display names for your enterprise'
 intro: 'You can choose whether the profile name (first and last name) of your enterprise members appear alongside their username across {% data variables.product.github %}.'
 versions:
   ghec: '*'
-  ghes: '*'
+  ghes: '>= 3.21'
 contentType: how-tos
 permissions: Enterprise and organization admins can configure whether profile names (first and last name) appear alongside usernames across {% data variables.product.github %}.
 shortTitle: Configure user display names

content/billing/reference/supported-payment-methods.md

@@ -44,7 +44,6 @@ The following Azure subscription types cannot be used as a payment method for {%
 | `DreamSpark_2015-02-01` | MS-AZR-0144P |
 | `AzurePass_2014-09-01` | MS-AZR-0120P, MS-AZR-0122P–MS-AZR-0125P, MS-AZR-0128P–MS-AZR-0130P |
 | `PayAsYouGo_2014-09-01` | MS-AZR-0017G |
-| `Sponsored_2016-01-01` | MS-AZR-0036P |
 
 {% ifversion fpt or ghec %}
 

content/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/applying-a-custom-security-configuration.md

@@ -24,6 +24,7 @@ After you create a {% data variables.product.prodname_custom_security_configurat
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. Optionally, in the "Apply configurations" section, filter for specific repositories you would like to apply your {% data variables.product.prodname_custom_security_configuration %} to. To learn how to filter the repository table, see [AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table).
 {% data reusables.security-configurations.select-repos %}
 1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **YOUR-CONFIGURATION-NAME**.

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/managing-your-github-advanced-security-license-usage.md

@@ -25,6 +25,7 @@ Before you can effectively manage your paid use of {% data variables.product.pro
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. In the "Apply configurations" section, your current license usage will be displayed. {% ifversion ghas-products %}This screenshot shows metered usage. If you have bought a volume/subscription license, then the number of licenses available is also reported.
 
     ![Screenshot of the "Apply configurations" section. The current license use for the enterprise is outlined in dark orange.](/assets/images/help/security-configurations/current-sp-cs-license-usage.png)

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-your-coverage/detaching-repositories-from-their-security-configurations.md

@@ -25,6 +25,7 @@ Alternatively, if you want to apply a {% data variables.product.prodname_securit
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. Optionally, in the "Apply configurations" section, filter for specific repositories you would like to detach from their configurations. To learn more, see [AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table).
 {% data reusables.security-configurations.select-repos %}
 1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **No configuration**.

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-your-coverage/filtering-repositories-in-your-organization-using-the-repository-table.md

@@ -21,6 +21,7 @@ You can filter the repository table in your organization to quickly find and man
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. In the "Apply configurations" section, use the **Search repositories** search bar to filter repositories in your organization in one of two ways:
     * Find repositories by name with free-text search
     * Select filters from the dropdown menu that appears once you click the search bar
@@ -30,6 +31,7 @@ You can filter the repository table in your organization to quickly find and man
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. To open the advanced filter dialog, in the "Apply configurations" section, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**.
 1. In the "Advanced filters" window, select the **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter** dropdown menu, then click a filter.
 1. To search for repositories matching the selected filter, fill out the available fields for that filter, then click **Apply**. You can repeat this process to add as many filters as you would like to your search.

content/code-security/reference/security-at-scale/troubleshoot-security-configurations/finding-repositories-with-attachment-failures.md

@@ -24,13 +24,14 @@ When an attachment failure happens:
 * Only some of the settings in the security configuration are applied to affected repositories.
 * Any changes you later make to the security configuration will not be inherited by the affected repositories.
 
-On the security configuration settings page, under "Apply configurations", you will see a banner advising how many repositories in your organization have an attachment failure, and an overview of the reason(s) for the failure.
+On the security configuration settings page, in the **Repositories** tab under "Apply configurations", you will see a banner advising how many repositories in your organization have an attachment failure, and an overview of the reason(s) for the failure.
 
 Click the link in the banner display, or alternatively, filter the list of repositories by `config-status:failed`, to see the list of affected repositories and to source additional guidance on how to remediate the attachment failure for a specific repository.
 
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.security-configurations.view-configurations-page %}
+1. Click the **Repositories** tab.
 1. In the "Apply configurations" section, filter by `config-status:failed`.
 1. From the results list, for the repository you're interested in, click **{% octicon "alert" aria-hidden="true" aria-label="alert" %} Failed REASON**.
 1. In the dialog box, review the information and follow the remediation guidance.

content/code-security/tutorials/trialing-github-advanced-security/enable-security-features-trial.md

@@ -28,7 +28,6 @@ When you planned your trial, you identified the features that you want to test a
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.advanced-security-tab %}
 1. Click **New configuration** to create a new configuration.
-1. To configure groups of security features for your repositories, click **Custom configuration**.
 1. Give the configuration a meaningful name and description.
 1. You will see that most features are already enabled. Review the features that are **Not set** and enable any that you want to trial, for example: "Automatic dependency submission."
 1. In the "Policy" area, set the "Use as default for newly created repositories" option as needed to define whether or not to apply the configuration to new repositories created in the enterprise.
@@ -64,7 +63,7 @@ You may find it helpful to apply an enterprise security configuration to all rep
 1. Click the **Settings** tab to display the organization settings.
 1. In the sidebar, click **{% data variables.product.UI_advanced_security %}** and then **Configurations** to display the security configurations page.
 1. Optionally, select the **Apply to** dropdown menu and click either **All repositories**, to apply any configuration to all repositories in the organization, or **All repositories without configurations**, to configure just the repositories in the organization without an existing security configuration.
-1. Optionally, in the "Apply configurations" section use the "Search repositories" field or **Filter** button to filter repositories. Then select one or more repositories and use the **Apply configuration** button to choose a configuration to apply to those repositories.
+1. Optionally, click the **Repositories** tab, then in the "Apply configurations" section, use the "Search repositories" field or **Filter** button to filter repositories. Then select one or more repositories and use the **Apply configuration** button to choose a configuration to apply to those repositories.
 
 For more information, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration).
 

content/copilot/concepts/agents/github-copilot-app.md

@@ -0,0 +1,70 @@
+---
+title: About the GitHub Copilot app
+shortTitle: GitHub Copilot app
+intro: 'The {% data variables.copilot.github_copilot_app %} is a desktop application for agent-driven development that brings parallel workstreams, {% data variables.product.github %} integration, and PR lifecycle management into one place.'
+product: '{% data reusables.gated-features.github-app %}'
+versions:
+  feature: copilot
+contentType: concepts
+redirect_from:
+  - /copilot/concepts/agents/github-app
+category:
+  - Learn about Copilot
+---
+
+> [!NOTE] The {% data variables.copilot.github_copilot_app %} is in {% data variables.release-phases.technical_preview %} and subject to change.
+>
+> * **{% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %} users** — Download and install from the [{% data variables.copilot.github_copilot_app %} repository](https://gh.io/github-copilot-app-repo?utm_source=docs-github-copilot-app-overview&utm_medium=docs&utm_campaign=github-copilot-app-tech-preview-2026) if your organization or enterprise has enabled preview features and {% data variables.copilot.copilot_cli_short %}.
+> * **{% data variables.copilot.copilot_pro_short %} and {% data variables.copilot.copilot_pro_plus_short %} users** — To request access, [join the waitlist](https://gh.io/github-copilot-app?utm_source=docs-github-copilot-app-overview&utm_medium=docs&utm_campaign=github-copilot-app-tech-preview-2026).
+
+## Introduction
+
+The {% data variables.copilot.github_copilot_app %} is a desktop application purpose-built for agent-driven development. It gives you a single place to direct AI agents across parallel workstreams, work with {% data variables.product.github %} issues and pull requests, and manage the full development lifecycle—without context-switching between terminals, IDEs, and browser tabs.
+
+The app is built on {% data variables.copilot.copilot_cli %} and integrates natively with {% data variables.product.github %}, so your repositories, branches, and CI pipelines work out of the box. It's designed for workflows where you want to run multiple agents in parallel and stay focused on directing work rather than doing it all yourself.
+
+## Supported operating systems
+
+The {% data variables.copilot.github_copilot_app %} supports the following operating systems:
+
+* macOS
+* Linux
+* Windows
+
+## Benefits of using the {% data variables.copilot.github_copilot_app %}
+
+* **Work in parallel.** Run multiple agent sessions at the same time, each on its own branch, so you can make progress on several tasks without waiting for one to finish.
+* **Stay in one place.** Triage issues, direct agents, review changes, and land pull requests without switching between your terminal, IDE, and browser.
+* **Start fast.** The app connects to {% data variables.product.github %} natively—your repositories, branches, issues and pull requests work out of the box with no additional setup.
+* **Stay in control.** Choose how much autonomy to give agents, from fully collaborative to fully autonomous, and adjust the model and reasoning effort for each session.
+
+## What can I do with the {% data variables.copilot.github_copilot_app %}?
+
+* **Parallel workspaces.** Run multiple isolated agent sessions simultaneously, each with a dedicated git worktree and branch.
+* **Session modes.** Choose how you work with agents: Interactive (collaborative), Plan (agent plans, you approve), or Autopilot (fully autonomous).
+* **{% data variables.product.github %} integration.** Browse and find issues, start sessions from them, create and close pull requests, review pull requests, and view CI check results—all within the app.
+* **Model choice.** Select from multiple LLMs and adjust reasoning effort per session.
+* **Customizations.** Configure MCP servers, skills, extensions, and plugins for each session.
+* **Scheduled workflows.** Save recurring agent tasks and run them on a schedule or on demand.
+* **Quick chats.** Brainstorm in a conversation mode without creating a dedicated branch or workspace.
+* **Search.** Search for issues or pull requests across your repositories directly from the app.
+
+## {% data variables.copilot.github_copilot_app %} workflow
+
+A typical workflow in the {% data variables.copilot.github_copilot_app %} looks like this:
+
+1. Browse issues in a repository and pick one up, or start from a blank workspace.
+1. Choose a session mode—Interactive, Plan, or Autopilot—and select a model.
+1. Describe the task and let the agent create a branch, write code, and run tests.
+1. Review the agent's changes, provide feedback, and iterate.
+1. Create a pull request, leave a review, check whether CI passed, and merge the PR—all from within the app.
+
+You can run several of these workflows in parallel, each in its own workspace, and switch between them as needed.
+
+## Providing feedback
+
+The {% data variables.copilot.github_copilot_app %} is in {% data variables.release-phases.public_preview %}. To share feedback, click the **Give feedback** icon in the bottom-left corner of the app.
+
+## Further reading
+
+* [AUTOTITLE](/copilot/how-tos/github-copilot-app/getting-started)

content/copilot/concepts/agents/index.md

@@ -8,6 +8,7 @@ versions:
 children:
   - /cloud-agent
   - /copilot-cli
+  - /github-copilot-app
   - /code-review
   - /copilot-memory
   - /hooks