Skip to content

Commit 147397b

Browse files
heathduttonheathdutton
authored
Merge branch 'github:main' into patch-1
2 parents 48de77c + 282d8d7 commit 147397b

File tree

11 files changed

+307
-11
lines changed

11 files changed

+307
-11
lines changed

‎CHANGELOG.md‎

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

33
**16 January 2026**
44

5+
The following new articles support the public preview release of Copilot Memory:
6+
7+
* [About agentic memory for GitHub Copilot](https://docs.github.com/copilot/concepts/agents/copilot-memory)
8+
* [Enabling and curating Copilot Memory](https://docs.github.com/copilot/how-tos/use-copilot-agents/copilot-memory)
9+
10+
<hr>
11+
12+
**16 January 2026**
13+
514
We published [About user offboarding on GitHub Enterprise Cloud](https://docs.github.com/en/enterprise-cloud@latest/admin/concepts/identity-and-access-management/user-offboarding) to give enterprise customers clear guidance about offboarding processes. The article covers recommended offboarding methods, the effects of offboarding, and what happens when a user is removed from all organizations in an enterprise.
615

716
We also updated [Removing a member from your enterprise](https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise) and [Removing a member from your organization](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization) to include instructions for enterprises that use Enterprise Managed Users or SCIM for organizations.

‎content/admin/concepts/enterprise-fundamentals/automations-in-your-enterprise.md‎

Lines changed: 135 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,135 @@
1+
---
2+
title: Automations in your enterprise
3+
shortTitle: Automations
4+
intro: 'Learn how {% data variables.product.prodname_github_apps %}, external services, and {% data variables.product.prodname_actions %} work together to automate processes in your enterprise.'
5+
versions:
6+
feature: enterprise-apps-public-beta
7+
type: overview
8+
topics:
9+
- Enterprise
10+
- Fundamentals
11+
---
12+
13+
Automation on {% data variables.product.github %} typically involves multiple components working together. The most important {% data variables.product.github %} native components are:
14+
15+
* **{% data variables.product.prodname_actions %} workflows**, which provide a runtime for executing automation logic. Out of the box, they work within a single repository, but they can be extended to automate across or even outside of repositories.
16+
* **{% data variables.product.prodname_github_apps %}**, which do not have a runtime. Instead, they provide identity, permissions, and event delivery so your automations, whether external services or workflows, can authenticate and act securely.
17+
18+
Most enterprise automation use {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_actions %} together. For example, a workflow running in {% data variables.product.prodname_actions %} may use a {% data variables.product.prodname_github_app %} to obtain a short-lived token that allows it to perform tasks across repositories or organizations.
19+
20+
This guide explains how {% data variables.product.prodname_github_apps %}, external automations, and {% data variables.product.prodname_actions %} complement each other, and when to use each in your enterprise.
21+
22+
## {% data variables.product.prodname_github_apps %}
23+
24+
A {% data variables.product.prodname_github_app %} provides the **identity, permissions, and webhook events** required for automation on or across repositories, organizations, or your enterprise. {% data variables.product.prodname_github_apps %} themselves do **not** execute logic, they enable other systems to do so.
25+
26+
{% data variables.product.prodname_github_apps %} support enterprise automation by offering:
27+
28+
* **Granular permissions** to follow least-privilege principles
29+
* **Scoped installations** at the enterprise, organization, or repository level
30+
* **Short-lived tokens** for secure access
31+
* **Distinct identities** with full auditability
32+
* **Delegated administration** through the {% data variables.product.prodname_github_app %} manager role
33+
* **Consistency at scale** when owned by the enterprise account
34+
35+
### What do {% data variables.product.prodname_github_apps %} enable?
36+
37+
{% data variables.product.prodname_github_apps %} allow **automations you write elsewhere**—such as external services or workflow steps—to act on {% data variables.product.github %} APIs within the permissions you grant. For example:
38+
39+
* Receiving webhook events and triggering external services
40+
* Enabling a workflow to act outside its default repository scope
41+
* Integrating {% data variables.product.github %} with third-party systems
42+
* Coordinating changes across many repositories
43+
* Running long-lived bots or services that monitor enterprise-level activity
44+
45+
{% ifversion enterprise-installed-apps %}
46+
47+
> [!NOTE]
48+
> Enterprise-installed {% data variables.product.prodname_github_apps %} cannot call every API endpoint. See [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-on-your-enterprise#what-enterprise-installed-apps-can-do).
49+
50+
{% endif %}
51+
52+
## {% data variables.product.prodname_actions %}
53+
54+
{% data variables.product.prodname_actions %} provide {% data variables.product.github %}’s built-in **runtime** for executing automation logic inside repositories. Workflows run on hosted or self-hosted runners and are ideal for tasks tied to code changes or repository events.
55+
56+
Use {% data variables.product.prodname_actions %} for:
57+
58+
* CI/CD (build, test, deploy)
59+
* Pull request checks and validations
60+
* Repository-level maintenance tasks
61+
* Event-driven workflows responding to pushes, tags, or issue updates
62+
* Scheduled jobs with cron
63+
64+
### How {% data variables.product.prodname_actions %} uses {% data variables.product.prodname_github_apps %}
65+
66+
{% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} are deeply connected:
67+
68+
* Workflow permissions map directly to {% data variables.product.prodname_github_app %} permissions.
69+
* Workflows can authenticate as a specific {% data variables.product.prodname_github_app %} using `actions/create-github-app-token`.
70+
* {% data variables.product.prodname_github_apps %} can trigger workflows through events such as `repository_dispatch`.
71+
72+
## External automations and services
73+
74+
External automations run outside {% data variables.product.github %} on your own infrastructure. These services typically:
75+
76+
* Receive webhook events from a {% data variables.product.prodname_github_app %}
77+
* Use the {% data variables.product.prodname_github_app %} to request short-lived installation tokens
78+
* Execute long-running or cross-enterprise logic
79+
* Integrate with external business systems
80+
81+
Examples include:
82+
83+
* Organization-wide configuration management
84+
* Policy enforcement services
85+
* Multi-repository code or metadata synchronization
86+
* Compliance report generation
87+
* Cross-organization issue or pull request management
88+
89+
All of these rely on {% data variables.product.prodname_github_apps %} for authentication, identity, and events—**not** for execution.
90+
91+
## How these components work together
92+
93+
Most enterprise automation uses a combination of {% data variables.product.prodname_github_apps %}, external services, and {% data variables.product.prodname_actions %} to achieve robust, scalable workflows.
94+
95+
For example:
96+
97+
1. An enterprise {% data variables.product.prodname_github_app %} receives a webhook when a new repository is created, and sends the webhook payload to a server where an external service is running.
98+
1. The external service standardizes required settings and provisions resources.
99+
1. The service triggers a {% data variables.product.prodname_actions %} workflow in the repository.
100+
1. The workflow performs CI, deploys templates, or configures scanning.
101+
102+
Each component handles a different layer of automation.
103+
104+
## When to use each type of automation
105+
106+
Use **a {% data variables.product.prodname_github_app %}** when you need:
107+
108+
* Authentication or permission to act across many repositories
109+
* Integration with external systems
110+
* Webhook-driven automations
111+
* Long-lived or enterprise-wide workflows
112+
* Auditability and identity separation
113+
114+
Use **external automations** when you need:
115+
116+
* Logic that runs continuously or outside {% data variables.product.github %}
117+
* Integration with internal systems
118+
119+
Use **{% data variables.product.prodname_actions %}** when you need:
120+
121+
* CI/CD pipelines
122+
* Repository-scoped automation
123+
* Automated checks tied to repository events
124+
* Execution of logic using {% data variables.product.github %}’s runner infrastructure
125+
126+
Use **{% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_actions %} together** when:
127+
128+
* A workflow must act beyond the repository’s default permissions
129+
* A {% data variables.product.prodname_github_app %} needs to trigger a workflow
130+
* External logic orchestrates in-repo execution
131+
* Enterprise-wide policies or workflows require both identity and runtime
132+
133+
## Next steps
134+
135+
Learn how to design and manage {% data variables.product.prodname_github_apps %} at the enterprise level in [AUTOTITLE](/admin/managing-your-enterprise-account/creating-github-apps-for-your-enterprise).

‎content/admin/concepts/enterprise-fundamentals/index.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,5 +11,6 @@ children:
1111
- /enterprise-accounts
1212
- /teams-in-an-enterprise
1313
- /roles-in-an-enterprise
14+
- /automations-in-your-enterprise
1415
contentType: concepts
1516
---

‎content/apps/using-github-apps/installing-a-github-app-on-your-enterprise.md‎

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -32,15 +32,7 @@ After installation, the app will be able to create an installation token for you
3232

3333
## What enterprise-installed apps can do
3434

35-
Enterprise-installed {% data variables.product.prodname_github_apps %} cannot call every enterprise API, but several APIs have already been updated to support GitHub Apps. These APIs and GraphQL mutations include:
36-
37-
* [List and create organizations in your enterprise](/graphql/reference/mutations#createenterpriseorganization)
38-
* [Manage users in your enterprise](/graphql/reference/objects#enterprise)
39-
* Create and manage {% data variables.product.prodname_github_app %} installations in your organizations
40-
* Manage enterprise custom repository properties
41-
* Call the enterprise SCIM APIs
42-
43-
Check the [changelog](https://github.blog/changelog/) for updates on new APIs and permissions for {% data variables.product.prodname_github_apps %}.
35+
{% data reusables.enterprise-accounts.enterprise-apps-capabilities %}
4436

4537
For more information about available permissions and API endpoints, see [AUTOTITLE](/rest/authentication/permissions-required-for-github-apps).
4638

‎content/copilot/concepts/copilot-metrics.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,19 @@ This means the data **does not include** activity from other {% data variables.p
5454

5555
License and seat management data are not included in {% data variables.product.prodname_copilot_short %} usage metrics reports. To view or manage license assignments, use the {% data variables.product.prodname_copilot_short %} user management API, which is the source of truth for license and seat information. See [AUTOTITLE](/rest/copilot/copilot-user-management).
5656

57+
## Why {% data variables.product.prodname_copilot_short %} usage metrics may differ across API resources
58+
59+
The following API resources expose {% data variables.product.prodname_copilot_short %}-related data, but they are not interchangeable and should not be compared directly. Each API resource is designed for a specific use case and data model, and differences in totals or coverage are expected. Use this table to understand which API resource best fits your reporting needs.
60+
61+
> [!NOTE]
62+
> We strongly recommend using the {% data variables.product.prodname_copilot_short %} usage metrics API for new integrations and analyses, as it provides the most complete and future-facing view of {% data variables.product.prodname_copilot_short %} usage.
63+
64+
| API resource | Scope | Key capabilities |
65+
| --- | --- | --- |
66+
| [AUTOTITLE](/rest/copilot/copilot-usage-metrics) | Advanced enterprise- and user-level event telemetry | Provides unified telemetry across completions, chat, and agent modes. Includes usage and lines of code metrics across all IDE modes, languages, and models. Supports detailed breakdowns by feature, IDE, language, model, and user, and is the primary API resource being actively developed and maintained. |
67+
| [AUTOTITLE](/rest/copilot/copilot-user-management) | License and seat assignment | Lists assigned {% data variables.product.prodname_copilot_short %} seats for an organization or enterprise, including license state, user association, and `last_activity_at`. This API resource is the source of truth for license and seat information. |
68+
| [AUTOTITLE](/rest/copilot/copilot-metrics) | Enterprise-, organization-, and team-level usage metrics | Provides aggregated usage data for {% data variables.product.prodname_copilot_short %} features on {% data variables.product.prodname_dotcom_the_website %} (such as pull request summaries) and some IDE-based completions and chat. Does not include Agent or Edit mode telemetry. Offers enterprise-wide and per-feature breakdowns by IDE and language. Does not include individual-level data. |
69+
5770
## How are metrics attributed across organizations?
5871

5972
> [!NOTE]

‎content/enterprise-onboarding/github-apps/automations-in-your-enterprise.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Automations in your enterprise
3+
shortTitle: Automations
4+
intro: 'Learn how {% data variables.product.prodname_github_apps %}, external services, and {% data variables.product.prodname_actions %} work together to automate processes in your enterprise.'
5+
versions:
6+
ghec: '*'
7+
type: overview
8+
topics:
9+
- Enterprise
10+
- Fundamentals
11+
---
12+
13+
{% data reusables.enterprise-onboarding.automations %}
14+
15+
## Next steps
16+
17+
To create {% data variables.product.prodname_github_apps %} that can access enterprise-level resources and automate workflows, see [AUTOTITLE](/enterprise-onboarding/github-apps/create-enterprise-apps).

‎content/enterprise-onboarding/github-apps/index.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ topics:
99
- Enterprise
1010
- GitHub Apps
1111
children:
12+
- /automations-in-your-enterprise
1213
- /create-enterprise-apps
1314
- /install-enterprise-apps
1415
---

‎data/reusables/code-scanning/require-actions-ghcs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
* {% data variables.product.prodname_actions %} are enabled.{% ifversion fpt or ghec %}
1+
* {% data variables.product.prodname_actions %} is enabled.{% ifversion fpt or ghec %}
22
* It is publicly visible, or {% data variables.product.prodname_GH_code_security %} is enabled.{%- elsif ghes %}
33
* {% data variables.product.prodname_GH_code_security %} is enabled.{% endif %}

‎data/reusables/enterprise-accounts/enterprise-apps-capabilities.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
Enterprise-installed {% data variables.product.prodname_github_apps %} cannot call every enterprise API, but several APIs have already been updated to support {% data variables.product.prodname_github_apps %}. These APIs and GraphQL mutations include:
2+
3+
* [List and create organizations in your enterprise](/graphql/reference/mutations#createenterpriseorganization)
4+
* [Manage users in your enterprise](/graphql/reference/objects#enterprise)
5+
* Create and manage {% data variables.product.prodname_github_app %} installations in your organizations
6+
* Manage enterprise custom repository properties
7+
* Call the enterprise SCIM APIs
8+
9+
Check the [changelog](https://github.blog/changelog/) for updates on new APIs and permissions for {% data variables.product.prodname_github_apps %}.

‎data/reusables/enterprise-accounts/github-apps-tab.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1. In the left sidebar, click **{% octicon "apps" aria-hidden="true" %} GitHub Apps**.
1+
1. In the left sidebar, click **{% octicon "apps" aria-hidden="true" %} {% data variables.product.prodname_github_apps %}**.

0 commit comments

Comments
 (0)