Skip to content

Commit 0cd92ce

Browse files
chore(repo): sync from inner source
Sync from github/github-well-architected-internal (main) Source Repository: github/github-well-architected-internal Source Branch: main Source SHA: 323a37b44a05c5eb889dd882598c1ae5dadabbad Co-authored-by: well-architected-sync-bot[bot] <235114805+well-architected-sync-bot[bot]@users.noreply.github.com>
1 parent 50db8dd commit 0cd92ce

3 files changed

Lines changed: 23 additions & 18 deletions

File tree

content/library/overview/release-notes/2026-q2.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22

33
## 2026 Q2
44

5-
- **New Content: [Governing agents in GitHub Enterprise](/library/governance/recommendations/governing-agents/)** - Published governance and policy guidance for managing GitHub Copilot agents across the enterprise, covering policy configuration, security boundaries, MCP server governance, and audit pipelines
6-
- **New Content: [Essentials of governance and administration with GitHub Enterprise](/library/governance/recommendations/governance-administration-essentials/)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering GitHub structural components, user access models, org architecture strategies, policy baselines, and operational topics such as integrations, roles, and audit logging
7-
- **New Content: [Managing AI credits](/library/governance/recommendations/managing-ai-credits/)** - Published a FinOps-oriented guide for governing AI credit consumption across GitHub Enterprise, covering layered budgets design, cost attribution, usage guidance, and an operating cadence
5+
- **New Content: [Governing agents in GitHub Enterprise](../governance/recommendations/governing-agents)** - Published governance and policy guidance for managing GitHub Copilot agents across the enterprise, covering policy configuration, security boundaries, MCP server governance, and audit pipelines
6+
- **New Content: [Essentials of governance and administration with GitHub Enterprise](../governance/recommendations/governance-administration-essentials)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering GitHub structural components, user access models, org architecture strategies, policy baselines, and operational topics such as integrations, roles, and audit logging
7+
- **New Content: [Managing AI credits](../governance/recommendations/managing-ai-credits)** - Published a FinOps-oriented guide for governing AI credit consumption across GitHub Enterprise, covering layered budgets design, cost attribution, usage guidance, and an operating cadence
88
- **Deprecated: Managing GitHub Copilot Premium Request Units (PRUs)** - Retired the PRU enterprise admin playbook, replaced by the managing AI credits guidance
9-
- **New Content: [Governing agentic workflows with gh-aw and APM](/library/governance/recommendations/governing-agentic-workflows/)** - Published guidance for enterprises adopting sandboxed AI agents, GitHub Agentic Workflows (gh-aw), and Agent Package Manager (APM) to enforce execution isolation, dependency governance, and auditable agent runs in regulated environments
10-
- **Update: [Defending against dependency supply chain attacks](/library/application-security/recommendations/managing-dependency-threats/)** - Expanded trusted publishing registry coverage to include NuGet and Crates alongside npm, PyPI, and RubyGems
9+
- **New Content: [Governing agentic workflows with gh-aw and APM](../governance/recommendations/governing-agentic-workflows)** - Published guidance for enterprises adopting sandboxed AI agents, GitHub Agentic Workflows (gh-aw), and Agent Package Manager (APM) to enforce execution isolation, dependency governance, and auditable agent runs in regulated environments
10+
- **Update: [Defending against dependency supply chain attacks](../application-security/recommendations/managing-dependency-threats)** - Expanded trusted publishing registry coverage to include NuGet and Crates alongside npm, PyPI, and RubyGems

content/library/productivity/recommendations/adopting-copilot-at-scale.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -22,19 +22,19 @@ areas:
2222
# Classifications of industries who may be at different stages of the customer journey.
2323
verticals:
2424
- automotive
25-
- manufacturing
25+
- education
26+
- energy
2627
- finance
2728
- gaming
28-
- media
2929
- government
30-
- information-technology
3130
- healthcare
31+
- hospitality
32+
- information-technology
33+
- manufacturing
34+
- media
35+
- professional-service
3236
- retail
33-
- education
34-
- energy
3537
- telecommunications
36-
- hospitality
37-
- professional-services
3838

3939
# Individuals in key roles on the customer journey, typically consisting of one or more administrators and the end-user community.
4040
personas:
@@ -111,7 +111,7 @@ An example GitHub Copilot launch plan should include the following minimum eleme
111111
#### Launch week (week 0)
112112

113113
- Communicate the opportunity, benefits, and availability of GitHub Copilot to your organization
114-
- Provide on-demand [training](https://learn.microsoft.com/en-us/training/modules/introduction-to-github-copilot/) and [resources](https://docs.github.com/en/enterprise-cloud@latest/copilot/quickstart) for users to get started with GitHub Copilot
114+
- Provide on-demand [training](https://learn.microsoft.com/en-us/training/modules/introduction-to-github-copilot/) and [resources](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/quickstart) for users to get started with GitHub Copilot
115115

116116
#### Post-launch (weeks 1-4)
117117

@@ -122,7 +122,7 @@ An example GitHub Copilot launch plan should include the following minimum eleme
122122
#### Post-launch (weeks 5-8)
123123

124124
- Monitor GitHub Copilot adoption and activity metrics
125-
- Develop a GitHub Copilot reporting mechanism to track KPIs and derive meaningful insights about GitHub Copilot by using the [Copilot Usage API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage?apiVersion=2022-11-28) and [Copilot User Management API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-user-management?apiVersion=2022-11-28)
125+
- Develop a GitHub Copilot reporting mechanism to track KPIs and derive meaningful insights about GitHub Copilot by using the [Copilot usage metrics API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage-metrics?apiVersion=2022-11-28) and [Copilot User Management API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-user-management?apiVersion=2022-11-28)
126126
- Build on your GitHub Copilot Expert Hub with advanced training and resources specific to your organization
127127
- Gather feedback from users and iterate on your GitHub Copilot program
128128

@@ -146,7 +146,7 @@ GitHub offers many free resources to help users get started with GitHub Copilot:
146146
- [GitHub Copilot Learning Pathway](https://resources.github.com/learn/pathways/copilot/essentials/essentials-of-github-copilot/)
147147
- [GitHub Copilot Youtube Playlist](https://www.youtube.com/playlist?list=PL0lo9MOBetEHEHi9h0k_lPn0XZdEeYZDS)
148148
- [GitHub Copilot Blog Posts](https://github.blog/?s=copilot)
149-
- [GitHub Copilot Quickstart Documentation](https://docs.github.com/en/enterprise-cloud@latest/copilot/quickstart)
149+
- [GitHub Copilot Quickstart Documentation](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/quickstart)
150150

151151
To best prepare your existing team and future hires, consider offering a mix of instructor-led and on-demand Copilot enablement resources.
152152

@@ -184,10 +184,10 @@ GitHub Copilot licenses can be assigned in a few different ways, each with their
184184
3) Specific teams in an organization
185185
4) Specific teams in an enterprise
186186

187-
While assigning licenses out of a single organization can simplify license management, it restricts the granularity of Copilot telemetry data from the [Copilot Usage API endpoint for organizations](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage?apiVersion=2022-11-28#get-a-summary-of-copilot-usage-for-organization-members).
187+
While assigning licenses out of a single organization can simplify license management, it restricts the granularity of Copilot telemetry data from the [Copilot usage metrics API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage-metrics?apiVersion=2022-11-28#get-copilot-organization-usage-metrics).
188188
If you would like to track GitHub Copilot usage across your GitHub Organizations, consider assigning licenses to specific teams or individuals in those organizations.
189189

190-
<!-- PLACEHOLDER FOR COPILOT USAGE API ENDPOINT FOR TEAMS TRADE-OFFS -->
190+
<!-- PLACEHOLDER FOR COPILOT USAGE METRICS API ENDPOINT FOR TEAMS TRADE-OFFS -->
191191

192192
{{< callout type="info" >}}
193193
When a user receives a seat from multiple organizations in the same enterprise, GitHub takes care of deduplicating these seats before billing for the user.

docs/taxonomies.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,16 +81,21 @@ areas:
8181
# Classifications of industries who may be at different stages of the customer journey.
8282
verticals:
8383
- automotive
84+
- education
85+
- energy
8486
- finance
8587
- gaming
8688
- government
89+
- healthcare
90+
- hospitality
8791
- information-technology
8892
- manufacturing
8993
- media
94+
- mid-market
9095
- professional-service
9196
- retail
9297
- smb-corporate
93-
- mid-market
98+
- telecommunications
9499

95100
# Individuals in key roles on the customer journey, typically consisting of one or more administrators and the end-user community.
96101
personas:

0 commit comments

Comments
 (0)