Skip to content

Commit c4a991e

Browse files
docs-botdocs-bot
authored
Merge pull request #39452 from github/repo-sync
Repo sync
2 parents f7c187d + 49a6a68 commit c4a991e

File tree

24 files changed

+769
-80
lines changed

24 files changed

+769
-80
lines changed

‎CHANGELOG.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,29 @@
11
# Docs changelog
22

3+
**16 July 2025**
4+
5+
We've added documentation describing how to use the GraphQL API to create a new issue and, in the same request, assign the issue to Copilot coding agent.
6+
7+
See: [Using Copilot to work on an issue](https://docs.github.com/copilot/how-tos/agents/copilot-coding-agent/using-copilot-to-work-on-an-issue#assigning-an-issue-to-copilot-via-the-github-api).
8+
9+
<hr>
10+
11+
**16 July 2025**
12+
13+
We've updated the Copilot documentation to coincide with the release of an improved user interface for configuring the firewall for Copilot coding agent.
14+
15+
See: [Customizing or disabling the firewall for Copilot coding agent](https://docs.github.com/en/copilot/how-tos/agents/copilot-coding-agent/customizing-or-disabling-the-firewall-for-copilot-coding-agent).
16+
17+
<hr>
18+
19+
**16 July 2025**
20+
21+
We've updated the Copilot docs to coincide with the release of issue form support for Copilot Chat. When you use Copilot Chat to create an issue, an issue form will be used if there's an appropriate one in the repo. Previously only issue templates were supported.
22+
23+
See [Using GitHub Copilot to create issues](https://docs.github.com/copilot/how-tos/github-flow/using-github-copilot-to-create-issues).
24+
25+
<hr>
26+
327
**30 June 2025**
428

529
Many enterprise customers want to measure the downstream impact of Copilot on their company, looking beyond leading metrics like adoption and usage.

‎content/actions/concepts/runners/about-actions-runner-controller.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ redirect_from:
1313
- /actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller
1414
---
1515

16-
[Legal notice](#legal-notice)
17-
1816
## About {% data variables.product.prodname_actions_runner_controller %}
1917

2018
{% data reusables.actions.actions-runner-controller-about-arc %}

‎content/actions/concepts/runners/about-runner-scale-sets.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ topics:
1212
- Actions Runner Controller
1313
---
1414

15-
[Legal notice](#legal-notice)
16-
1715
## About runner scale sets
1816

1917
A runner scale set is a group of homogeneous runners that can be assigned jobs from {% data variables.product.prodname_actions %}. The number of active runners owned by a runner scale set can be controlled by auto-scaling runner solutions such as {% data variables.product.prodname_actions_runner_controller %} (ARC).

‎content/actions/how-tos/sharing-automations/creating-workflow-templates-for-your-organization.md

Lines changed: 3 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -16,29 +16,14 @@ type: tutorial
1616
topics:
1717
- Workflows
1818
- CI
19+
permissions: Write access to the organization's public `.github` repository. Templates can be used by organization members who have permission to create workflows.
1920
---
2021

2122
{% data reusables.actions.enterprise-github-hosted-runners %}
2223

23-
## Overview
24-
25-
{% data reusables.actions.workflow-organization-templates %}
26-
27-
{% data reusables.actions.workflow-templates-categories %}
28-
29-
> [!NOTE]
30-
> Because workflow templates require a public `.github` repository, they are not available for {% data variables.product.prodname_emus %}.
31-
32-
## Creating a workflow template
33-
34-
Workflow templates can be created by users with write access to the organization's _public_ `.github` repository. These can then be used by organization members who have permission to create workflows.
35-
36-
{% ifversion fpt %}
37-
Workflow templates created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use workflow templates to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-workflows/creating-starter-workflows-for-your-organization).
38-
{% endif %}
39-
4024
> [!NOTE]
41-
> To avoid duplication among workflow templates you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see [AUTOTITLE](/actions/using-workflows/reusing-workflows).
25+
> * Because workflow templates require a public `.github` repository, they are not available for {% data variables.product.prodname_emus %}.
26+
> * To avoid duplication among workflow templates you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see [AUTOTITLE](/actions/using-workflows/reusing-workflows).
4227
4328
This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the workflow templates will be presented to users when they are creating a new workflow.
4429

‎content/actions/reference/extending-github-actions-importer-with-custom-transformers.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ redirect_from:
1717
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/extending-github-actions-importer-with-custom-transformers
1818
---
1919

20-
[Legal notice](#legal-notice)
21-
2220
## About custom transformers
2321

2422
{% data variables.product.prodname_actions_importer %} offers the ability to extend its built-in mapping by creating custom transformers. Custom transformers can be used to:

‎content/actions/reference/supplemental-arguments-and-settings.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ redirect_from:
1515
- /actions/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/supplemental-arguments-and-settings
1616
---
1717

18-
[Legal notice](#legal-notice)
19-
2018
This article provides general information for configuring {% data variables.product.prodname_actions_importer %}'s supplemental arguments and settings, such as optional parameters, path arguments, and network settings.
2119

2220
## Optional parameters

‎content/actions/tutorials/actions-runner-controller/authenticating-arc-to-the-github-api.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ redirect_from:
1515
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/authenticating-to-the-github-api#deploying-using-personal-access-token-classic-authentication
1616
---
1717

18-
[Legal notice](#legal-notice)
19-
2018
You can authenticate {% data variables.product.prodname_actions_runner_controller %} (ARC) to the {% data variables.product.prodname_dotcom %} API by using a {% data variables.product.prodname_github_app %} or by using a {% data variables.product.pat_v1 %}.
2119

2220
> [!NOTE]

‎content/actions/tutorials/actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ redirect_from:
1515
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller
1616
---
1717

18-
[Legal notice](#legal-notice)
19-
2018
## Deploying a runner scale set
2119

2220
To deploy a runner scale set, you must have ARC up and running. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/quickstart-for-actions-runner-controller).

‎content/actions/tutorials/actions-runner-controller/quickstart-for-actions-runner-controller.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,6 @@ redirect_from:
1515
- /actions/tutorials/quickstart-for-actions-runner-controller
1616
---
1717

18-
[Legal notice](#legal-notice)
19-
20-
## Introduction
21-
22-
{% data reusables.actions.actions-runner-controller-about-arc %}
23-
24-
You can set up ARC on Kubernetes using Helm, then create and run a workflow that uses runner scale sets. For more information about runner scale sets, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller#runner-scale-set).
25-
2618
## Prerequisites
2719

2820
In order to use ARC, ensure you have the following.

‎content/actions/tutorials/actions-runner-controller/troubleshooting-actions-runner-controller-errors.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,6 @@ redirect_from:
1414
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors
1515
---
1616

17-
[Legal notice](#legal-notice)
18-
1917
## Logging
2018

2119
The {% data variables.product.prodname_actions_runner_controller %} (ARC) resources, which include the controller, listener, and runners, write logs to standard output (`stdout`). We recommend you implement a logging solution to collect and store these logs. Having logs available can help you or GitHub support with troubleshooting and debugging. For more information, see [Logging Architecture](https://kubernetes.io/docs/concepts/cluster-administration/logging/) in the Kubernetes documentation.

0 commit comments

Comments
 (0)