[pull] main from github:main

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics-for-github-enterprise-server.md

@@ -32,7 +32,7 @@ Plugins provide metrics to `collectd`. You can learn about each plugin available
 | `df` | Usage information about the instance's file system | [Plugin:DF](https://collectd.org/wiki/index.php/Plugin:DF) in the `collectd` wiki |
 | `disk` | Performance statistics for the instance's hard disks and other block devices | [Plugin:Disk](https://collectd.org/wiki/index.php/Plugin:Disk) in the `collectd` wiki |
 | `elasticsearch` | Statistics for Elasticsearch, which provides the instance's search functionality | [phobos182/collectd-elasticsearch](https://github.com/phobos182/collectd-elasticsearch/) repository on {% data variables.product.prodname_dotcom_the_website %} |
-| `fhcount` | Total, used, and unused file handles for the instance's Linux OS | [Manpage collectd.conf(5)](https://www.collectd.org/documentation/manpages/collectd.conf.html#plugin-fhcount) in the `collectd` wiki |
+| `fhcount` | Total, used, and unused file handles for the instance's Linux OS | [Manpage collectd.conf(5)](https://collectd.org/documentation/manpages/collectd.conf.html) in the `collectd` documentation |
 | `haproxy` | Front-end connections to the instance from HAProxy's management socket | [mleinart/collectd-haproxy](https://github.com/mleinart/collectd-haproxy) repository on {% data variables.product.prodname_dotcom_the_website %} |
 | `listener` | Active and queued connections to the instance's `github-unicorn`, `github-gitauth`, and `github-ernicorn` services | N/A |
 | `load` | System load average | [Plugin:Load](https://collectd.org/wiki/index.php/Plugin:Load) in the `collectd` wiki |

content/copilot/how-tos/use-copilot-agents/coding-agent/assign-copilot-to-an-issue.md

@@ -25,7 +25,7 @@ contentType: how-tos
 
 ## Introduction
 
-You can assign a {% data variables.product.github %} issue to {% data variables.product.prodname_copilot_short %}, just like you would with a human software developer. {% data variables.product.prodname_copilot_short %} will start working on the issue, raise a pull request and when it's finished working, request a review from you. For more information, see [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent).
+You can assign a {% data variables.product.github %} issue to {% data variables.product.prodname_copilot_short %}, just like you would with a human software developer. {% data variables.product.prodname_copilot_short %} will start working on the issue, on a branch it creates from the default branch of the repository. It will create a pull request and, when it's finished working, it will request a review from you. For more information, see [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent).
 
 If you haven't used {% data variables.product.prodname_copilot_short %} to work on an issue before, you can find some useful advice for getting good results in [AUTOTITLE](/copilot/tutorials/coding-agent/best-practices).
 

content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md

@@ -98,6 +98,8 @@ In your `copilot-setup-steps.yml` file, you can only customize the following set
 
 For more information on these options, see [AUTOTITLE](/actions/writing-workflows/workflow-syntax-for-github-actions#jobs).
 
+Any value that is set for the `fetch-depth` option of the `actions/checkout` action will be overridden to allow the agent to rollback commits upon request, while mitigating security risks. For more information, see [`actions/checkout/README.md`](https://github.com/actions/checkout/blob/main/README.md).
+
 Your `copilot-setup-steps.yml` file will automatically be run as a normal {% data variables.product.prodname_actions %} workflow when changes are made, so you can see if it runs successfully. This will show alongside other checks in a pull request where you create or modify the file.
 
 Once you have merged the yml file into your default branch, you can manually run the workflow from the repository's **Actions** tab at any time to check that everything works as expected. For more information, see [AUTOTITLE](/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow).

content/copilot/how-tos/use-copilot-agents/coding-agent/troubleshoot-coding-agent.md

@@ -106,6 +106,10 @@ If {% data variables.product.prodname_copilot_short %} tries to make a request w
 
 For more information, see [AUTOTITLE](/copilot/customizing-copilot/customizing-or-disabling-the-firewall-for-copilot-coding-agent).
 
+## {% data variables.product.prodname_copilot_short %} is not picking up attached screenshots
+
+The maximum image size allowed by {% data variables.copilot.copilot_coding_agent %} is 3.00 MiB. Images larger than this will be removed from the request.
+
 ## Further reading
 
 * [AUTOTITLE](/copilot/tutorials/coding-agent/best-practices)

content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md

@@ -57,12 +57,12 @@ User history for the above data | {% octicon "check" aria-label="Can be migrated
 Attachments (see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/attaching-files)) | {% octicon "check" aria-label="Can be migrated" %}  | {% octicon "check" aria-label="Can be migrated" %}  |
 Releases | {% octicon "x" aria-label="Cannot be migrated" %} | {% octicon "check" aria-label="Can be migrated" %}  |
 
-Different size limits per repository apply depending on your GHES version.
+Different size limits per repository apply to the compressed archive, depending on your GHES version.
 
-Limit | GHES <3.8.0 | GHES 3.8.0+ |
------ | ----------- | ----------- |
-Git source | 2GB | 10GB
-Metadata | 2GB | 10GB
+Limit | GHES <3.8.0 | GHES 3.8.x-3.11.x | GHES 3.12.x | GHES 3.13.0+
+----- | ----------- | ----------------- | ----------- | ------------
+Git source | 2GB | 10GB | 20GB | 40GB (public preview)
+Metadata | 2GB | 10GB | 20GB | 40GB (public preview)
 
 ### Data that is not migrated
 

data/reusables/repositories/about-ruleset-insights.md

@@ -6,4 +6,6 @@ On the "Rule Insights" page, you will see a timeline of the following user actio
 
 If a ruleset is running in "Evaluate" mode, you can see actions that would have passed or failed if the ruleset had been active.
 
+Additonally these insights are availible via the rule suites [REST API](/rest/repos/rule-suites).
+
 ![Screenshot of the "Rule Insights" page. Three actions are listed marked: "Pass," "Bypass," and "Fail". The failed action has with an "evaluate" label.](/assets/images/help/repository/rule-insights.png)