Merge pull request #46153 from github/repo-sync

Repo sync

Author: docs-bot

content/billing/reference/github-license-users.md

@@ -51,6 +51,9 @@ category:
   * {% data variables.product.company_short %} counts each outside collaborator once, even if the user account has access to multiple repositories in your organization.
 * Dormant users who are a member or owner of at least one organization in the enterprise
 
+> [!IMPORTANT]
+> With usage-based billing, changes to license consumption during a billing cycle are reflected in your next bill. A user who consumed a license at any point during the cycle, for example before being suspended or removed, remains billable for that cycle. See [AUTOTITLE](/billing/concepts/enterprise-billing/usage-based-licenses#how-are-metered-licenses-measured).
+
 If your enterprise does not use {% data variables.product.prodname_emus %} or usage-based billing, you will also be billed for each of the following accounts. Under usage-based billing, pending invitations do not consume a license. See [AUTOTITLE](/billing/concepts/enterprise-billing/usage-based-licenses).
 
 * Anyone with a pending invitation to become an organization owner or member

content/code-security/concepts/code-scanning/setup-types.md

@@ -13,11 +13,23 @@ category:
 
 ## About default setup
 
-Default setup for {% data variables.product.prodname_code_scanning %} is the quickest, easiest, most low-maintenance way to enable {% data variables.product.prodname_code_scanning %} for your repository. Based on the code in your repository, default setup will automatically create a custom {% data variables.product.prodname_code_scanning %} configuration. You can also customize this configuration, including at scale across your organization, without creating or maintaining a workflow file. See [Customization of default setup](#customization-of-default-setup). After enabling default setup, the code written in {% data variables.product.prodname_codeql %}-supported languages in your repository will be scanned using {% data variables.product.prodname_codeql %}:
+Default setup for {% data variables.product.prodname_code_scanning %} is the quickest, easiest, most low-maintenance way to enable {% data variables.product.prodname_code_scanning %} for your repository. Based on the code in your repository, default setup will automatically create a custom {% data variables.product.prodname_code_scanning %} configuration. You can also customize this configuration, including at scale across your organization, without creating or maintaining a workflow file. See [Customization of default setup](#customization-of-default-setup).
 
+With default setup, the code written in {% data variables.product.prodname_codeql %}-supported languages in your repository will be scanned using {% data variables.product.prodname_codeql %}:
+
+* When you enable it.
 * On each push to the repository's default branch, or any protected branch. For more information on protected branches, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches).
 * When creating or committing to a pull request based against the repository's default branch, or any protected branch, excluding pull requests from forks.
-* On a weekly schedule.
+* On a weekly schedule{% ifversion code-scanning-scheduled-scan-activity %}, if a push or pull request has triggered a scan in the last 180 days{% endif %}.
+{%- ifversion code-scanning-inactive-repos %}
+* Every 30 days for inactive repositories, when enabled by an organization owner. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings#continuing-scans-on-inactive-repositories).
+{%- endif %}
+
+{% ifversion code-scanning-scheduled-scan-activity %}
+
+Weekly scheduled scans start only after a push or pull request triggers a scan with default setup enabled. The initial scan and scans triggered by configuration or language changes do not start or extend the weekly schedule. Pushes and pull requests from before default setup was enabled do not count.
+
+{% endif %}
 
 ### Supported languages
 

content/code-security/how-tos/maintain-quality-code/enable-code-quality.md

@@ -56,3 +56,9 @@ For the available access options, and how filtering and enforcement work, see [A
 Your changes are saved automatically and begin to propagate immediately. In large organizations, it can take several minutes for the changes to apply across all repositories.
 
 If you're rolling out the feature across many teams, we recommend you pilot on a small group and tune your quality thresholds before you enable everywhere. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/roll-out-at-scale).
+
+## Scan frequency after enablement
+
+When you enable {% data variables.product.prodname_code_quality_short %}, an initial {% data variables.product.prodname_codeql %} scan runs on the default branch. Weekly scheduled {% data variables.product.prodname_codeql %} scans start only after a push or pull request triggers a scan. Pushes and pull requests from before enablement do not count as activity.
+
+Weekly scheduled scans pause if no push or pull request has triggered a scan in the last 180 days. Initial scans, scans triggered by configuration or language changes, and scheduled scans do not count as activity. A new push- or pull-request-triggered scan resumes the weekly schedule.

content/communities/setting-up-your-project-for-healthy-contributions/adding-an-accessibility-page-to-your-repository.md

@@ -0,0 +1,41 @@
+---
+title: Adding an accessibility page to your repository
+intro:  'Add an `ACCESSIBILITY.md` file to make your project''s accessibility information easy to find and give people a clear way to report barriers.'
+versions:
+  feature: accessibility-pages
+shortTitle: Add an accessibility page
+category:
+  - Set up your project for contributions
+---
+
+When a repository contains an `ACCESSIBILITY.md` file, {% data variables.product.github %} displays an **Accessibility** tab on the repository overview and links to the page from the repository's **About** section.
+
+{% data variables.product.github %} looks for the file in the `.github` directory, the repository root, and the `docs` directory, in that order. If the repository does not contain an accessibility page, it can inherit one from a repository named `.github` that is owned by the organization.
+
+An accessibility page can describe your project's accessibility priorities, supported environments, known barriers, contributor expectations, reporting process, ownership, and maintenance.
+
+{% ifversion fpt or ghec %}
+## Adding an accessibility page from Community Standards
+
+For a public repository, you can start with the accessibility page template.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+1. In the left sidebar, click **Community Standards**.
+1. Under "Additional community file," find "Accessibility," then click **Add** or **Propose**.
+1. Replace the instructions in the template with accessibility-related information for your project. The instructions are stored in comments and do not appear when GitHub renders the file.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_new_file %}
+{% endif %}
+
+## Creating an accessibility page manually
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.files.add-file %}
+1. In the file name field, type _ACCESSIBILITY.md_. To store the file in the `.github` or `docs` directory, type _.github/ACCESSIBILITY.md_ or _docs/ACCESSIBILITY.md_.
+1. On the **Edit new file** tab, add accessibility-related information.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_new_file %}

content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md

@@ -61,6 +61,9 @@ You can create defaults in your organization or personal account for the followi
 
 | Community health file | Description |
 | --- | --- |
+| {% ifversion accessibility-pages %} |
+| _ACCESSIBILITY.md_ | An ACCESSIBILITY file describes a project's accessibility goals, known barriers, and reporting process. For more information, see [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-an-accessibility-page-to-your-repository). |
+| {% endif %} |
 | _CODE_OF_CONDUCT.md_ | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project). |
 | _CONTRIBUTING.md_ | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors). |
 | Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms). |

content/communities/setting-up-your-project-for-healthy-contributions/index.md

@@ -16,6 +16,7 @@ children:
   - /accessing-a-projects-community-profile
   - /adding-a-code-of-conduct-to-your-project
   - /setting-guidelines-for-repository-contributors
+  - /adding-an-accessibility-page-to-your-repository
   - /adding-a-license-to-a-repository
   - /adding-support-resources-to-your-project
   - /creating-a-default-community-health-file

content/copilot/concepts/agents/computer-use.md

@@ -0,0 +1,82 @@
+---
+title: About computer use in GitHub Copilot
+shortTitle: Computer use
+intro: '{% data variables.product.prodname_copilot_short %} can interact with desktop applications to automate tasks that cannot be completed with a more direct tool.'
+versions:
+  feature: copilot
+contentType: concepts
+category:
+  - Learn about Copilot
+---
+
+> [!NOTE]
+> {% data reusables.copilot.computer-use-preview-note %}
+
+## About computer use
+
+{% data variables.product.prodname_copilot_short %} can interact with desktop applications on your behalf by reading accessible application content and visual context, clicking controls, entering and editing text, pressing keys, scrolling, dragging, and navigating workflows across applications.
+
+Computer use is available in {% data variables.copilot.copilot_cli %} and {% data variables.copilot.github_copilot_app %} on macOS and Windows.
+
+Computer use expands the tasks {% data variables.product.prodname_copilot_short %} can help automate, including workflows in legacy and GUI-only software that do not provide an API, command-line interface, or MCP integration.
+
+Computer use can help you complete tasks such as:
+
+* Reviewing and summarizing information in a legacy desktop application.
+* Updating content in a presentation.
+* Entering or updating information in GUI-only software.
+* Moving information between applications as part of a multi-step workflow.
+
+> [!TIP]
+> Computer use is designed for tasks that require interaction with a visual interface. If an API, MCP server, terminal command, filesystem tool, or dedicated browser tool can complete the task directly, that tool typically provides more structured information and predictable results.
+
+## Capabilities
+
+When enabled, computer use allows {% data variables.product.prodname_copilot_short %} to:
+
+* Read accessible application content and visual context through your operating system's accessibility tree or screenshots when visual context is needed.
+* Click controls.
+* Enter and edit text.
+* Press keys, scroll, and drag items.
+* Navigate workflows across applications.
+
+The agent selects these tools as it works through your prompt. You can review tool activity in the session.
+
+## Controlling access for computer use
+
+Computer use is disabled by default. You must enable it before an agent can use its tools.
+
+Computer use follows the tool permission settings for the {% data variables.product.prodname_copilot_short %} surface where your session is running. These settings determine whether {% data variables.product.prodname_copilot_short %} asks for approval before controlling a desktop application. You can change the tool permission settings for each surface. If prompted to approve access to an application, you can grant access for the current session, save the approval for future sessions, or deny access.
+
+If you choose **Always allow** for a specific application, {% data variables.product.prodname_copilot_short %} stores the decision locally. The decision applies to both {% data variables.copilot.copilot_cli %} and {% data variables.copilot.github_copilot_app %} on the same computer. In the app, you can review the list of always allowed applications and remove individual approvals. Removing an application deletes its saved approval for future sessions in both the app and CLI. It does not revoke access already granted in a running session.
+
+Permission rules that deny a tool take precedence over automatic or saved approvals.
+
+Enterprise administrators can disable computer use through managed settings. Enabling computer use locally does not override an enterprise policy. For configuration details, see [AUTOTITLE](/copilot/reference/enterprise-administrators/enterprise-managed-settings#featurescomputeruse).
+
+You can interrupt an active operation if computer use starts acting unexpectedly. In {% data variables.copilot.copilot_cli %}, press <kbd>Esc</kbd> twice. In {% data variables.copilot.github_copilot_app %}, click **Stop** or press <kbd>Esc</kbd>.
+
+On macOS, computer use guides you through granting:
+
+* **Accessibility** permission to interact with application controls.
+* **Screen Recording** permission to inspect application windows when visual context is needed.
+
+## Limitations and risks
+
+Computer use interprets interfaces that can change between application versions, operating systems, and window states. It can select the wrong control, enter text in the wrong location, or have difficulty with non-standard or dynamic controls and complex workflows. Changes in timing or window state can produce different results, cause computer use to repeat an action, or prevent it from continuing.
+
+> [!WARNING]
+> Computer use can automate interactions across desktop applications, but it also introduces security risks. Ambiguous instructions or unexpected on-screen content may cause unintended actions that affect your device, data, or connected accounts, including access to personal, financial, or enterprise systems. Computer use is not a substitute for human judgment. Review the target application, requested permissions, and result, particularly before allowing actions that modify data or affect other people.
+
+Application windows may display sensitive information, including information about other people. Only use computer use with applications and tasks whose visible content you are comfortable providing as context to {% data variables.product.prodname_copilot_short %}.
+
+If you choose **Always allow** for an application, later computer-use actions can control it without asking again. Avoid choosing **Always allow** for applications that contain sensitive information or support high-impact actions.
+
+For comprehensive information about responsible use, see [AUTOTITLE](/copilot/responsible-use/agents).
+
+## Next steps
+
+To enable and use computer use, see:
+
+* [AUTOTITLE](/copilot/how-tos/github-copilot-app/computer-use)
+* [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/computer-use)

content/copilot/concepts/agents/copilot-cli/about-copilot-cli.md

@@ -120,6 +120,10 @@ The following sections provide examples of tasks you can complete with {% data v
 
   `You said: "The application is now running on http://localhost:3002 and is fully functional!" but when I browse to that URL I get "This site can't be reached"`
 
+### Computer use
+
+In local sessions on macOS and Windows, you can enable computer use to let {% data variables.product.prodname_copilot_short %} interact with desktop applications. This capability is useful for workflows in legacy and GUI-only software that do not provide an API, command-line interface, or MCP integration. For more information, see [AUTOTITLE](/copilot/concepts/agents/computer-use).
+
 ### Tasks involving {% data variables.product.prodname_dotcom_the_website %}
 
 * Fetch and display details about your work from {% data variables.product.prodname_dotcom_the_website %}.