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
{{ message }}
Repository navigation
Commit 095d720
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: content/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ There are two ways to qualify for free access to {% data variables.copilot.copil
26
26
27
27
{% data variables.product.company_short %} reevaluates your eligibility every month.
28
28
29
+
{% data reusables.copilot.free-access-cancellation-note %} For more information about managing your plan, see [AUTOTITLE](/copilot/how-tos/manage-your-account/view-and-change-your-copilot-plan).
30
+
29
31
## What if I don't qualify for free access to {% data variables.copilot.copilot_pro_short %}?
30
32
31
33
If you do not meet the previous criteria, you can do one of the following:
Copy file name to clipboardExpand all lines: content/copilot/how-tos/manage-your-account/view-and-change-your-copilot-plan.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
@@ -65,7 +65,7 @@ You can upgrade or downgrade your {% data variables.product.prodname_copilot_sho
65
65
66
66
You can cancel your {% data variables.product.prodname_copilot_short %} plan at any time. You’ll retain access to your current features until your billing cycle ends. You will automatically be downgraded to {% data variables.copilot.copilot_free_short %} at the end of your billing cycle.
67
67
68
-
If you have been granted free access to {% data variables.product.prodname_copilot_short %} as a verified student, teacher, or maintainer of a popular open source project, you won’t be able to cancel your plan. If you have access to {% data variables.product.prodname_copilot_short %} through an organization or enterprise, you will not be able to cancel your plan. In these cases, you can disable {% data variables.product.prodname_copilot_short %} in your environment. See [AUTOTITLE](/copilot/how-tos/configure-personal-settings/configure-in-ide).
68
+
{% data reusables.copilot.free-access-cancellation-note %} If you have access to {% data variables.product.prodname_copilot_short %} through an organization or enterprise, you will not be able to cancel your plan. In these cases, you can disable {% data variables.product.prodname_copilot_short %} in your environment. See [AUTOTITLE](/copilot/how-tos/configure-personal-settings/configure-in-ide).
69
69
70
70
{% data reusables.copilot.copilot-one-account-short %}
Copy file name to clipboardExpand all lines: content/copilot/reference/copilot-usage-metrics/copilot-usage-metrics.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,7 +158,7 @@ Active-user counts:
158
158
|`weekly_passive_copilot_code_review_users`|`integer`| No | Number of unique users who had {% data variables.copilot.copilot_code-review_short %} automatically assigned to review their pull request during a trailing seven-day window, with no active engagement. |
159
159
|`monthly_passive_copilot_code_review_users`|`integer`| No | Number of unique users who had {% data variables.copilot.copilot_code-review_short %} automatically assigned to review their pull request during a trailing 28-day window, with no active engagement. |
160
160
|`daily_active_cli_users`|`integer`| Yes | Number of unique users who used {% data variables.copilot.copilot_cli_short %} on a given day. This count is **independent** of IDE active-user counts and is **not** included in IDE-based active-user definitions. Omitted for enterprises or organizations with no CLI usage that day. |
161
-
|`daily_active_copilot_app_users`|`integer`| Yes | Number of unique users who used the {% data variables.copilot.github_copilot_app_short %} on a given day. Enterprise reports only. Null when the enterprise has no {% data variables.copilot.github_copilot_app_short %} activity that day. |
161
+
|`daily_active_copilot_app_users`|`integer`| Yes | Number of unique users who used the {% data variables.copilot.github_copilot_app_short %} on a given day. Null when the enterprise or organization has no {% data variables.copilot.github_copilot_app_short %} activity that day. |
162
162
163
163
Activity totals and breakdowns:
164
164
@@ -177,7 +177,7 @@ Activity totals and breakdowns:
177
177
|`totals_by_language_model`|`array`| No | Aggregated language-and-model activity breakdown. See [Activity breakdown objects](#activity-breakdown-objects). |
178
178
|`totals_by_model_feature`|`array`| No | Aggregated model-and-feature activity breakdown. See [Activity breakdown objects](#activity-breakdown-objects). |
179
179
|`totals_by_cli`|`object`| Yes | Aggregated {% data variables.copilot.copilot_cli_short %} metrics for the day. Omitted when there is no CLI usage that day. Unlike the per-user form, it does not include `last_known_cli_version`. See [{% data variables.copilot.copilot_cli_short %} metrics fields](#copilot-cli-metrics-fields). |
180
-
|`totals_by_copilot_app`|`object`| Yes | Aggregated {% data variables.copilot.github_copilot_app_short %} metrics for the day. Enterprise reports only. Null when the enterprise has no {% data variables.copilot.github_copilot_app_short %} activity that day. See [{% data variables.copilot.github_copilot_app_short %} metrics fields](#copilot-app-metrics-fields). |
180
+
|`totals_by_copilot_app`|`object`| Yes | Aggregated {% data variables.copilot.github_copilot_app_short %} metrics for the day. Null when the enterprise or organization has no {% data variables.copilot.github_copilot_app_short %} activity that day. See [{% data variables.copilot.github_copilot_app_short %} metrics fields](#copilot-app-metrics-fields). |
181
181
|`totals_by_3rd_party_agent`|`array`| Yes | Aggregated per-agent usage metrics for recognized {% data variables.copilot.agent_apps %}. Omitted when the enterprise or organization had no recognized {% data variables.copilot.agent_app %} activity that day. See [{% data variables.copilot.agent_apps_caps %} metrics fields](#agent-apps-metrics-fields). |
182
182
|`totals_by_ai_adoption_phase`|`array`| Yes | Per-phase aggregates of users and their average activity. Omitted when no adoption-phase data is available. See [AI adoption phase fields](#ai-adoption-phase-fields). |
183
183
|`pull_requests`|`object`| No | Daily pull request activity for the enterprise or organization. See [Pull request activity fields](#pull-request-activity-fields). |
@@ -366,6 +366,8 @@ Each entry in the aggregated `totals_by_ai_adoption_phase` array contains:
366
366
|`avg_pull_requests_merged`|`number`| No | Average pull requests merged per user in this phase. |
367
367
|`total_pull_requests_merged`|`integer`| No | Total pull requests merged by users in this phase. Applies to the organization day and enterprise day aggregated reports. |
368
368
|`avg_pull_requests_median_minutes_to_merge`|`number`| No | Average of the per-user median minutes to merge for users in this phase. |
369
+
|`avg_pull_requests_minutes_to_review`|`number`| No | Median time in minutes from pull request creation to first review, scoped to merged pull requests and attributed to the pull request's merge day. |
370
+
|`avg_pull_requests_review_cycles`|`number`| No | Median number of review submissions (review cycles) per pull request, scoped to merged pull requests and attributed to the pull request's merge day. |
Copy file name to clipboardExpand all lines: content/copilot/reference/copilot-usage-metrics/example-schema.md
+97-2Lines changed: 97 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,11 @@ The following are example schemas for the user-level, enterprise-level, and repo
19
19
20
20
```json copy
21
21
[{
22
+
"ai_adoption_phase": {
23
+
"phase": "Phase 2",
24
+
"phase_number": 2,
25
+
"version": "v1"
26
+
},
22
27
"ai_credits_used": 12.5,
23
28
"code_acceptance_activity_count": 3,
24
29
"code_generation_activity_count": 3,
@@ -124,6 +129,10 @@ The following are example schemas for the user-level, enterprise-level, and repo
124
129
"used_chat": false,
125
130
"used_cli": true,
126
131
"used_copilot_app": true,
132
+
"used_copilot_cloud_agent": false,
133
+
"used_copilot_code_review_active": null,
134
+
"used_copilot_code_review_passive": null,
135
+
"used_copilot_coding_agent": false,
127
136
"user_id": 1,
128
137
"user_login": "login1",
129
138
"user_initiated_interaction_count": 1,
@@ -135,6 +144,8 @@ The following are example schemas for the user-level, enterprise-level, and repo
135
144
136
145
Organization per-user reports use the same `totals_by_3rd_party_agent` entry fields and also include `organization_id`. Per-user entries do not include `session_count`.
137
146
147
+
In this example, `used_copilot_code_review_active` and `used_copilot_code_review_passive` are `null` because there was no {% data variables.copilot.copilot_code-review_short %} signal for the user that day. `used_copilot_cloud_agent` and `used_copilot_coding_agent` always carry the same value.
148
+
138
149
## Enterprise-level schema example
139
150
140
151
```json copy
@@ -144,7 +155,10 @@ Organization per-user reports use the same `totals_by_3rd_party_agent` entry fie
144
155
"code_generation_activity_count" : 4,
145
156
"daily_active_cli_users" : 2,
146
157
"daily_active_copilot_app_users" : 1,
158
+
"daily_active_copilot_cloud_agent_users" : 1,
159
+
"daily_active_copilot_code_review_users" : 1,
147
160
"daily_active_users" : 2,
161
+
"daily_passive_copilot_code_review_users" : 0,
148
162
"day" : "2025-10-01",
149
163
"enterprise_id" : "1",
150
164
"loc_added_sum" : 54,
@@ -153,7 +167,10 @@ Organization per-user reports use the same `totals_by_3rd_party_agent` entry fie
153
167
"loc_suggested_to_delete_sum" : 6,
154
168
"monthly_active_agent_users" : 0,
155
169
"monthly_active_chat_users" : 0,
170
+
"monthly_active_copilot_cloud_agent_users" : 1,
171
+
"monthly_active_copilot_code_review_users" : 1,
156
172
"monthly_active_users" : 2,
173
+
"monthly_passive_copilot_code_review_users" : 0,
157
174
"pull_requests" : {
158
175
"median_minutes_to_merge" : 2.5,
159
176
"median_minutes_to_merge_copilot_authored" : 2.5,
@@ -181,6 +198,39 @@ Organization per-user reports use the same `totals_by_3rd_party_agent` entry fie
| Actions settings | Repository-level GitHub Actions configuration, including allowed actions and permissions |
29
29
| Autolinks | Custom autolink references |
30
-
| Branch protections | Branch protection rules |
30
+
| Branch protections | Branch protection rules are partially migrated, with the limitations described below |
31
31
| Pages | GitHub Pages configuration |
32
32
33
+
> [!WARNING]
34
+
> Branch protection migration is partially supported. {% data variables.product.prodname_elm_short %} preserves whether actor restrictions are enabled for dismissing pull request reviews and pushing to protected branches, but it does not preserve the permitted users, teams, or apps. A push restriction can therefore be recreated on the destination with an empty allowlist. It also does not migrate pull request bypass actors, force-push actors, status check app bindings, matching-branch creation restrictions, merge queue settings, deployment requirements, or branch locking. Review and update migrated branch protection rules before allowing users to work in the destination repository.
35
+
33
36
### Git data, LFS, and wikis
34
37
35
38
| Resource | Notes |
@@ -96,7 +99,7 @@ The only organization-level action supported by {% data variables.product.prodna
96
99
| Data | Notes |
97
100
|---|---|
98
101
| Repository defaults | N/A |
99
-
| Repository rulesets |Only branch protection rules are migrated. |
102
+
| Repository rulesets |Repository rulesets are not migrated. Branch protection rules are partially migrated. |
100
103
| Pull requests from forks | N/A |
101
104
| Pending pull request reviews | Only submitted reviews are migrated. |
102
105
@@ -127,7 +130,7 @@ The following tables document which resource types support live updates and whic
The branch protection limitations described in [Repository settings and configuration](#repository-settings-and-configuration) apply to both the initial migration and live updates.
141
145
142
146
> [!NOTE]
143
147
> When a pull request review is submitted, {% data variables.product.prodname_elm_short %} imports the full review including all inline comments together. Inline comments that are part of an initial review submission are migrated correctly. However, **replies added to a review thread after the review has been submitted** are not captured as live updates and will not appear in the migrated repository.
If you have been granted free access to {% data variables.product.prodname_copilot_short %} as a verified student, teacher, or maintainer of a popular open source project, you won’t be able to cancel your plan.
0 commit comments