Skip to content

Commit 3aa6bda

Browse files
authored
Remove hardcoded next steps for AI governance (#61106)
1 parent a93dc7a commit 3aa6bda

9 files changed

Lines changed: 2 additions & 36 deletions

File tree

content/copilot/get-started/resources-for-approval.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,3 @@ Even if you're only using {% data variables.product.github %} to grant access to
6868
## Further questions
6969

7070
If teams have questions that aren't addressed by these resources, contact your account manager or {% data variables.contact.contact_enterprise_sales %}.
71-
72-
## Next steps
73-
74-
Once teams have signed off on {% data variables.product.prodname_copilot_short %}, you can choose a plan for your enterprise. See [AUTOTITLE](/copilot/get-started/choose-enterprise-plan).

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -62,11 +62,4 @@ If your enterprise has a {% data variables.copilot.copilot_enterprise_short %} p
6262
* If your enterprise has a {% data variables.copilot.copilot_business_short %} plan, click **Enabled**.
6363
* If your enterprise has a {% data variables.copilot.copilot_enterprise_short %} plan, click either **Copilot: Enterprise** or **Copilot: Business** to assign a specific Copilot plan to the organization.
6464

65-
### Next steps
66-
6765
After you've enabled {% data variables.product.prodname_copilot_short %} for an organization in your enterprise, owners of the organization can grant access to some or all members of the organization. See [AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/managing-access-for-copilot-business-in-your-organization).
68-
69-
## Further reading
70-
71-
* [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)
72-
* [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/monitor-agentic-activity.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,4 @@ category:
2323
{% data reusables.enterprise-accounts.ai-controls-tab %}
2424
1. To see a list of agentic activity in your enterprise over the last 180 days, at the bottom of the page, click {% octicon "log" aria-hidden="true" aria-label="log" %} **Audit logs**.
2525

26-
## Next steps
27-
2826
For help interpreting the audit log events for agentic activity, see [AUTOTITLE](/copilot/reference/agentic-audit-log-events).

content/copilot/how-tos/administer-copilot/manage-for-enterprise/review-audit-logs.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,3 @@ To view a record of agent activity, use the `actor:Copilot` search term. See [AU
4949
## Retaining audit log history
5050

5151
The audit log retains events for the last 180 days. We recommend streaming the audit log to a Security Information and Event Management (SIEM) platform, where you can view long-term history and set up alerts for anomalous activity. See [AUTOTITLE](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
52-
53-
## Further reading
54-
55-
* [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)

content/copilot/how-tos/copilot-cli/administer-copilot-cli-for-your-enterprise.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ shortTitle: Administer for enterprise
44
intro: 'Control the use of {% data variables.copilot.copilot_cli_short %} within your enterprise.'
55
versions:
66
feature: copilot
7+
permissions: Enterprise owners and AI managers
78
contentType: how-tos
89
allowTitleToDifferFromFilename: true
910
category:
@@ -15,7 +16,7 @@ docsTeamMetrics:
1516

1617
## Enabling or disabling {% data variables.copilot.copilot_cli_short %}
1718

18-
**Enterprise owners** can control the use of {% data variables.copilot.copilot_cli_short %} by configuring a policy.
19+
You can control the use of {% data variables.copilot.copilot_cli_short %} by configuring a policy.
1920

2021
{% data reusables.enterprise-accounts.access-enterprise %}
2122
{% data reusables.enterprise-accounts.ai-controls-tab %}

content/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-enterprise.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,3 @@ If your enterprise is on {% data variables.enterprise.data_residency_site %}, us
4949
{% data reusables.copilot.enterprise-licensing %}
5050

5151
For instructions, see [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/enabling-copilot-for-organizations-in-your-enterprise).
52-
53-
## Next steps
54-
55-
{% data reusables.copilot.setup-next-steps %}

content/copilot/tutorials/cloud-agent/build-guardrails.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,3 @@ Review the default permissions for the `GITHUB_TOKEN` in your enterprise. See [A
7272
This policy does **not** affect the token that {% data variables.product.prodname_copilot_short %} will receive for its sessions, but the `GITHUB_TOKEN` _is_ used in environment setup steps defined in `copilot-setup-steps.yml` workflow files.
7373

7474
Bear in mind that developers will be able to set their own `permissions` in these workflow files, and you should encourage them to use the minimum required permissions in all workflows.
75-
76-
## Next steps
77-
78-
When you're ready to enable {% data variables.copilot.copilot_cloud_agent %}, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/manage-copilot-coding-agent).

content/copilot/tutorials/roll-out-at-scale/establish-ai-managers.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -69,9 +69,3 @@ If you have created a ruleset targeting {% data variables.copilot.agent_profiles
6969

7070
1. In the "Bypass list" section, select the {% octicon "plus" aria-hidden="true" aria-label="plus" %} **Add bypass** dropdown menu, then click your AI management team.
7171
1. At the bottom of the page, click **Save changes**.
72-
73-
## Next steps
74-
75-
Now that you have established AI managers for your enterprise, help them customize and manage your enterprise's AI experience by sharing the following resources:
76-
* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies)
77-
* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/test-custom-agents)

content/copilot/tutorials/roll-out-at-scale/maintain-codebase-standards.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,3 @@ To prepare for these scenarios, you should plan for how you will address problem
8484
## 7. Check code quality
8585

8686
If you're confident in your governance model but still concerned that {% data variables.product.prodname_copilot_short %} will reduce the quality of your codebase over time, you can measure this over the course of a rollout. If enabled, {% data variables.product.prodname_code_quality %} provides metrics on the code health of your repositories. See [AUTOTITLE](/code-security/concepts/about-code-quality).
87-
88-
## Next steps
89-
90-
Understand how your enterprise can use the audit log to monitor changes to configuration settings and license assignment. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-audit-logs).

0 commit comments

Comments
 (0)