You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ type: how_to
15
15
16
16
## About the idle timeout
17
17
18
-
A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create, or to existing codespaces the next time you start them. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
18
+
A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
19
19
20
20
> [!WARNING]
21
21
> Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing).
Copy file name to clipboardExpand all lines: content/copilot/concepts/copilot-metrics.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ Metrics are available through:
25
25
26
26
* The {% data variables.product.prodname_copilot_short %} usage metrics APIs, which provide detailed, user-level data you can export for further analysis.
27
27
* The {% data variables.product.prodname_copilot_short %} usage metrics dashboard, which visualizes 28-day usage trends across your enterprise.
28
+
* The code generation dashboard, which breaks down how code is being generated by users and agents across your enterprise.
28
29
* The {% data variables.product.prodname_copilot_short %} usage metrics NDJSON export, which offers raw data for custom BI tools or long-term storage.
29
30
30
31
For a complete list of available metrics and data fields, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics).
@@ -89,6 +90,8 @@ Look for patterns across these signals rather than focusing on any single number
89
90
90
91
## Next steps
91
92
92
-
Now that you understand what each {% data variables.product.prodname_copilot_short %} metric measures and how to use them, you can explore the dashboard to see these metrics in action.
93
+
Now that you understand what each {% data variables.product.prodname_copilot_short %} metric measures and how to use them, you can explore the dashboards to see these metrics in action.
93
94
94
-
To learn how to access and interpret these metrics in the {% data variables.product.prodname_copilot_short %} usage metrics dashboard, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/view-usage-and-adoption).
95
+
* To view adoption and usage trends across your enterprise, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/view-usage-and-adoption).
96
+
* To analyze how code is being generated by users and agents, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/view-code-generation).
97
+
* To access these metrics programmatically, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
intro: You can use the code generation dashboard to monitor how {% data variables.product.prodname_copilot_short %} generates code across your enterprise, including activity from both users and agents.
5
+
permissions: '{% data reusables.copilot.usage-metrics-permissions %}'
6
+
versions:
7
+
feature: copilot
8
+
topics:
9
+
- Copilot
10
+
contentType: how-tos
11
+
allowTitleToDifferFromFilename: true
12
+
---
13
+
14
+
{% data reusables.copilot.usage-metrics-preview %}
15
+
16
+
The code generation dashboard shows how {% data variables.product.prodname_copilot_short %} is generating code across your enterprise. By comparing user-initiated and agent-initiated activity across models, languages, and modes, you can see how teams are adopting AI-assisted and agent-driven development.
17
+
18
+
## Prerequisite
19
+
20
+
"{% data variables.product.prodname_copilot_short %} usage metrics" must be enabled on the AI Control tab. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies#defining-policies-for-your-enterprise).
21
+
22
+
## Accessing the dashboard
23
+
24
+
{% data reusables.copilot.access-copilot-metrics-dashboard %}
25
+
1. In the left sidebar, click **Code generation**.
26
+
27
+
## What you can view
28
+
29
+
The dashboard shows aggregated code generation activity across your enterprise, including:
30
+
31
+
***Lines of code changed with AI**. The total lines of code added and deleted across all modes.
32
+
***User-initiated code changes**. Lines suggested or manually added through completions and chat actions.
33
+
***Agent-initiated code changes**. Lines automatically added or deleted by agents across edit, agent, and custom modes.
34
+
***Activity by model and language**. User-initiated and agent-initiated activity grouped by model and language.
35
+
36
+
For a full list of available metrics and definitions, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/copilot-usage-metrics#code-generation-dashboard-metrics).
37
+
38
+
## Next steps
39
+
40
+
* To explore adoption and usage trends across your enterprise, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/view-usage-and-adoption).
41
+
* To understand how Lines of Code (LoC) metrics are measured and what affects their accuracy and coverage, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/lines-of-code-metrics).
42
+
* To access usage data programmatically, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
Copy file name to clipboardExpand all lines: content/copilot/how-tos/administer-copilot/manage-for-enterprise/view-usage-and-adoption.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Viewing the Copilot usage metrics dashboard
3
3
shortTitle: View usage and adoption
4
-
intro: You can use the {% data variables.product.prodname_copilot_short %} usage metrics dashboard to monitor adoption and usage trends across your enterprise.
4
+
intro: You can use the {% data variables.product.prodname_copilot_short %} usage metrics dashboard to monitor how developers across your enterprise are adopting and using {% data variables.product.prodname_copilot_short %}.
5
5
permissions: '{% data reusables.copilot.usage-metrics-permissions %}'
6
6
versions:
7
7
feature: copilot
@@ -22,6 +22,7 @@ After your initial rollout, the {% data variables.product.prodname_copilot_short
22
22
## Accessing the dashboard
23
23
24
24
{% data reusables.copilot.access-copilot-metrics-dashboard %}
25
+
1. In the left sidebar, click **{% data variables.product.prodname_copilot_short %} usage**.
25
26
26
27
Data in the dashboard is based only on IDE telemetry and may appear up to three full UTC days behind the current date. See [AUTOTITLE](/copilot/concepts/copilot-metrics#data-freshness).
27
28
@@ -38,3 +39,4 @@ For deeper analysis, you can export NDJSON reports from the dashboard and use {%
38
39
39
40
* To learn how to interpret the data in each chart and act on usage trends, see [AUTOTITLE](/copilot/reference/interpret-copilot-metrics).
40
41
* To learn how to track license activation and initial usage of {% data variables.product.prodname_copilot %} with usage metrics, see [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/assign-licenses/track-usage-and-adoption).
42
+
* To access usage data programmatically, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
Copy file name to clipboardExpand all lines: content/copilot/reference/copilot-usage-metrics/copilot-usage-metrics.md
+20-4Lines changed: 20 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ topics:
15
15
16
16
{% data reusables.copilot.usage-metrics-preview %}
17
17
18
-
The {% data variables.product.prodname_copilot_short %} usage metrics dashboard and APIs display and export data using a consistent set of fields. This reference lists all available metrics and describes how to interpret their values in both dashboard visuals and NDJSON or API exports.
18
+
The {% data variables.product.prodname_copilot_short %} usage metrics dashboard and APIs display and export data using a consistent set of fields. This reference lists all available metrics and describes how to interpret their values in both dashboard visuals and NDJSON or API exports. To retrieve this data programmatically, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
19
19
20
20
For guidance on how to read and interpret these metrics, see [AUTOTITLE](/copilot/concepts/copilot-metrics).
21
21
22
-
## Dashboard metrics
22
+
## {% data variables.product.prodname_copilot_short %} usage dashboard metrics
23
23
24
24
These metrics appear directly in the {% data variables.product.prodname_copilot_short %} usage dashboard.
25
25
@@ -41,10 +41,26 @@ These metrics appear directly in the {% data variables.product.prodname_copilot_
41
41
| Most used chat model | The most frequently used chat model in the current calendar month. |
42
42
| Requests per chat mode | Number of chat requests by mode (Ask, Edit, Agent). |
43
43
44
+
## Code generation dashboard metrics
45
+
46
+
These metrics appear in the code generation dashboard and provide a breakdown of how code is being generated across user-initiated and agent-initiated activity. All values are derived from lines of code (LoC) added or deleted in the IDE.
47
+
48
+
| Metric | Description |
49
+
|:--|:--|
50
+
| Lines of code changed with AI | Total lines of code added and deleted across all modes during the current calendar month. |
51
+
| Agent contribution | Percentage of lines of code added and deleted by agents (including Edit, Agent, and custom modes) during the current calendar month. |
52
+
| Average lines deleted by agent | Average number of lines automatically deleted by agents on behalf of active users during the current calendar month. |
53
+
| Daily total of lines added and deleted | Total number of lines added to and deleted from the codebase across all modes for each day. |
54
+
| User-initiated code changes | Lines suggested or manually added by users through code completions and chat panel actions (insert, copy, or apply). |
55
+
| Agent-initiated code changes | Lines automatically added to or deleted from the codebase by agents on behalf of users across Edit, Agent, and custom modes. |
56
+
| User-initiated code changes per model | User-initiated lines of code, grouped by model used in the IDE. |
57
+
| Agent-initiated code changes per model | Agent-initiated lines of code, grouped by model performing the agent actions. |
58
+
| User-initiated code changes per language | User-initiated lines of code, grouped by programming language. |
59
+
| Agent-initiated code changes per language | Agent-initiated lines of code, grouped by programming language. |
60
+
44
61
## API and export fields
45
62
46
-
These fields appear in the exported NDJSON reports and in the {% data variables.product.prodname_copilot_short %} usage metrics APIs.
47
-
They provide granular daily records for each user in the enterprise.
63
+
These fields appear in the exported NDJSON reports and in the {% data variables.product.prodname_copilot_short %} usage metrics APIs. They provide granular daily records for each user in the enterprise.
Copy file name to clipboardExpand all lines: content/copilot/reference/copilot-usage-metrics/interpret-copilot-metrics.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,12 @@ redirect_from:
14
14
- /copilot/reference/interpret-copilot-metrics
15
15
---
16
16
17
-
>[!NOTE] The {% data variables.product.prodname_copilot %} usage metrics dashboard is currently in {% data variables.release-phases.public_preview %} and subject to change.
17
+
>[!NOTE] The {% data variables.product.prodname_copilot_short %} usage metrics dashboard is currently in {% data variables.release-phases.public_preview %} and subject to change.
18
18
19
19
After you’ve viewed usage data in the {% data variables.product.prodname_copilot_short %} usage metrics dashboard, you can use this article to interpret what each chart means and identify opportunities to increase adoption and engagement across your enterprise.
20
20
21
+
You can also access these metrics programmatically through the {% data variables.product.prodname_copilot_short %} usage metrics REST API, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
22
+
21
23
## Reviewing overall usage trends
22
24
23
25
Use the main usage charts in the dashboard to understand overall adoption and engagement patterns across your enterprise. These charts help you identify where usage is growing, leveling off, or declining, so you can take action to maintain engagement.
{% data reusables.copilot.usage-metrics-preview %}
18
18
19
-
Lines of Code (LoC) metrics offer a directional way to measure {% data variables.product.prodname_copilot_short %}’s tangible output. These metrics quantify how many lines {% data variables.product.prodname_copilot_short %} suggested, added, or deleted in the editor—helping key stakeholders and decision makers understand {% data variables.product.prodname_copilot_short %}’s contribution to the codebase over time.
19
+
Lines of Code (LoC) metrics provide a directional measure of {% data variables.product.prodname_copilot_short %}’s output by quantifying the lines it suggested, added, or deleted across completions, chat, and agent features.
20
+
21
+
## Where LoC metrics appear
22
+
23
+
You may encounter LoC metrics in:
24
+
25
+
***Code generation dashboard** — visualizes LoC-based user and agent activity. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/view-code-generation).
26
+
***Exports and APIs** — expose LoC fields such as `loc_suggested_to_add_sum`, `loc_added_sum`, and `loc_deleted_sum`. See [AUTOTITLE](/rest/copilot/copilot-usage-metrics).
27
+
***"Data available in {% data variables.product.prodname_copilot_short %} usage metrics" reference** — lists all dashboard and API fields derived from LoC. See [AUTOTITLE](/copilot/reference/copilot-usage-metrics/copilot-usage-metrics).
28
+
29
+
This article covers how LoC is measured and what affects its accuracy and coverage. For detailed definitions, refer to the reference article above.
30
+
31
+
## Considerations for LoC metrics
20
32
21
33
LoC metrics may vary across IDEs and versions. Keep the following considerations in mind:
22
34
@@ -43,17 +55,6 @@ LoC metrics require specific minimum versions of IDEs and {% data variables.prod
* The {% data variables.product.prodname_copilot_short %} user-level report
51
-
* The {% data variables.product.prodname_copilot_short %} usage metrics API
52
-
53
-
They are **not** included in the {% data variables.product.prodname_copilot_short %} usage metrics dashboard.
54
-
55
-
LoC metrics measure {% data variables.product.prodname_copilot_short %}’s activity across completions, chat, and agent features. For detailed field descriptions and definitions, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/copilot-usage-metrics#api-and-export-fields).
56
-
57
58
## How agent mode affects LoC metrics
58
59
59
60
Unlike completions or chat, {% data variables.copilot.copilot_agent_short %} does not follow a “suggest then accept” flow. Agents plan and execute multi-step tasks, often editing multiple files iteratively without explicit acceptance by the user. Because of this, LoC metrics for agent activity are measured differently.
intro: '{% data variables.contact.special_events_support %} is an optional support offering for {% data variables.product.prodname_enterprise %} customers who need dedicated assistance during critical events.'
5
+
versions:
6
+
ghec: '*'
7
+
ghes: '*'
8
+
topics:
9
+
- Support
10
+
---
11
+
12
+
## About {% data variables.contact.special_events_support %}
13
+
14
+
When your business is preparing for a major televised event, election, retail launch, or other high-stakes enterprise milestone—whether that means maintaining continuity or supporting seasonal traffic—{% data variables.product.github %}’s {% data variables.contact.special_events_support %} provides dedicated expertise to help you manage increased demands.
15
+
16
+
At {% data variables.product.github %}, we work to understand customers and their evolving operational requirements. {% data variables.contact.special_events_support %} offers focused, time-bound support designed to help teams prepare for, monitor, and respond to activity surrounding business-critical events.
17
+
18
+
## What's included with {% data variables.contact.special_events_support %}?
19
+
20
+
{% data variables.contact.special_events_support %} provides tailored 24- or 48-hour support packages led by Support Engineers. These packages include:
21
+
22
+
* Strategic pre-event planning and system health checks to make sure you’re prepared.
23
+
* Rapid, real-time response via a designated channel throughout your event.
24
+
* Post-event debriefs with actionable recommendations to drive future success.
25
+
26
+
## How {% data variables.contact.special_events_support %} works
27
+
28
+
{% data variables.contact.special_events_support %} is available to all {% data variables.product.prodname_enterprise %} customers. {% data variables.contact.premium_support %} customers can add this offering for additional support coverage during critical moments.
29
+
30
+
The service uses a simple booking process and first-come, first-served scheduling. It offers a flexible, time-bound option for organizations that need additional support capacity during high-impact events.
31
+
32
+
## Signing up for {% data variables.contact.special_events_support %}
33
+
34
+
To sign up for {% data variables.contact.special_events_support %}, [contact our account management team](https://enterprise.github.com/contact).
0 commit comments