Merge pull request #36674 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md

@@ -64,98 +64,6 @@ You will need to update the configuration of your self-hosted runners to use the
 * In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application.
 * Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/removing-self-hosted-runners) and [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners).
 
-## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits
-
-{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.location.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings.
-
-You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI.
-
-### 1. Check the overall CPU and memory usage in the management console
-
-Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards).
-
-If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources).
-
-### 2. Check the Nomad Jobs CPU and memory usage in the management console
-
-If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs.
-
-Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for:
-
-* `mps_frontend`
-* `mps_backend`
-* `token_frontend`
-* `token_backend`
-* `actions_frontend`
-* `actions_backend`
-
-If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit.
-
-### 3. Increase the resource allocation for services at their limit
-
-1. Log in to the administrative shell using SSH. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh).
-1. Run the following command to see what resources are available for allocation:
-
-   ```shell
-   nomad node status -self
-   ```
-
-   In the output, find the "Allocated Resources" section. It looks similar to the following example:
-
-   ```text
-   Allocated Resources
-   CPU              Memory          Disk
-   7740/49600 MHZ   23 GiB/32 GiB   4.4 GiB/7.9 GiB
-   ```
-
-   For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation.
-
-   > [!WARNING]
-   > Be careful not to allocate more than the total available resources, or services will fail to start.
-
-1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`:
-
-   ```shell
-   cd /etc/consul-templates/etc/nomad-jobs/actions
-   ```
-
-   In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above:
-
-   * `mps.hcl.ctmpl`
-   * `token.hcl.ctmpl`
-   * `actions.hcl.ctmpl`
-1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following:
-
-   ```text
-   resources {
-     cpu = 512
-     memory = 2048
-     network {
-       port "http" { }
-     }
-   }
-   ```
-
-   The values are in MHz for CPU resources, and MB for memory resources.
-
-   For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to:
-
-   ```text
-   resources {
-     cpu = 1024
-     memory = 4096
-     network {
-       port "http" { }
-     }
-   }
-   ```
-
-1. Save and exit the file.
-1. Run `ghe-config-apply` to apply the changes.
-
-    When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/<name>.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`.
-1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational.
-
 ## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows
 
 {% data reusables.dependabot.dependabot-on-actions-troubleshooting-workflows %} For more information, see [Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions) below.

content/copilot/using-github-copilot/guides-on-using-github-copilot/index.md

@@ -12,4 +12,5 @@ children:
   - /refactoring-code-with-github-copilot
   - /using-copilot-to-migrate-a-project
   - /writing-tests-with-github-copilot
+  - /modernizing-legacy-code-with-github-copilot
 ---