Skip to content

Commit 2b8fc80

Browse files
authored
Merge pull request #44555 from github/repo-sync
Repo sync
2 parents 6f3f728 + c04b815 commit 2b8fc80

2 files changed

Lines changed: 19 additions & 3 deletions

File tree

content/copilot/how-tos/copilot-on-github/set-up-copilot/configure-runners.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,3 +71,21 @@ By default, {% data variables.copilot.copilot_code-review_short %} runs on a sta
7171
runs-on: ubuntu-4-core
7272
# ...
7373
```
74+
75+
## Configure runners at the organization level
76+
77+
Organization owners can set a default runner type for {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} across all repositories in the organization, and control whether individual repositories can override this default.
78+
79+
> [!NOTE]
80+
> The organization-level runner type applies to both {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %}. Repositories can still override the organization default using `copilot-setup-steps.yml` unless you disable **Allow repositories to customize the runner type**. For more information, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent#preventing-repositories-from-customizing-the-runner-type).
81+
82+
This is useful if your organization requires all code reviews and {% data variables.copilot.copilot_cloud_agent_short %} tasks to run on specific runners, for example, to use larger runners for better performance or self-hosted runners that have access to internal resources.
83+
84+
{% data reusables.profile.access_org %}
85+
{% data reusables.profile.org_settings %}
86+
1. In the sidebar, under "Code, planning, and automation," click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **Runner type**.
87+
1. Next to "Runner type configuration," click {% octicon "pencil" aria-label="Edit" %}.
88+
1. In the "Edit runner type" dialog, select the runner type to use by default across your organization, then click **Save runner selection**.
89+
* **Standard {% data variables.product.prodname_dotcom %} runner**: {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} will use the standard {% data variables.product.prodname_dotcom %}-hosted runner.
90+
* **Labeled runner**: {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} will use a runner matching the label you specify.
91+
1. Optionally, to prevent individual repositories from overriding the organization-level runner configuration using their `copilot-setup-steps.yml` file, disable **Allow repositories to customize the runner type**.

content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,8 @@ The {% data variables.product.prodname_copilot %} integration in Jira allows you
2424
## Prerequisites
2525

2626
* You must have a {% data variables.product.github %} account with access to {% data variables.product.prodname_copilot_short %} through a paid {% data variables.product.prodname_copilot_short %} plan.
27-
* You must have a Jira Cloud account with the following AI features enabled for your organization:
27+
* You must have a Jira Cloud account with the following AI feature enabled for your organization:
2828
* **Jira must be an AI-enabled app** and Rovo must be activated. See [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation.
29-
* **Beta AI features** must be turned on. See [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation.<!-- markdownlint-disable-line GHD046 -->
3029
* Installation and authentication must be completed for both Jira and {% data variables.product.github %}.
3130

3231
> [!NOTE]
@@ -148,7 +147,6 @@ If you run into problems, try the following solutions.
148147
In Jira, check your Atlassian Administration settings for your organization are set as follows.
149148
150149
1. Jira is an AI-enabled app, see [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation.
151-
1. Beta AI features are enabled, see [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation.<!-- markdownlint-disable-line GHD046 -->
152150
153151
### You can see the {% data variables.copilot.copilot_cloud_agent %} but it is not possible to assign it to a Jira work item
154152

0 commit comments

Comments
 (0)