jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-07 00:01:39 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #33710 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2024-06-26 00:57:42 -07:00
committed by GitHub
parent 0182c53b4a 36e911decd
commit b3534c616c
1 changed files with 22 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
content/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-github-copilot-activity-in-your-organization/reviewing-usage-data-for-github-copilot-in-your-organization.md
View File

@@ -36,6 +36,28 @@ redirect_from:
You can use {% data variables.product.prodname_dotcom %}'s REST API to get details about the assignment of {% data variables.product.prodname_copilot %} seats in your organization. See "[Get Copilot seat information and settings for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-information-and-settings-for-an-organization)," "[List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#list-all-copilot-seat-assignments-for-an-organization)," and "[Get Copilot seat assignment details for a user](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-assignment-details-for-a-user)."
## Understanding the `last_activity_at` calculation
{% note %}
**Note:** This data is in public beta and subject to change.
{% endnote %}
To align the `last_activity_at` data point with _actual usage_, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are:
* Receiving a code suggestion in an IDE
* Chatting with Copilot Chat in an IDE
{%- ifversion ghec %}
* Creating or updating a knowledge base
* Creating a pull request summary
* Interacting with Copilot Chat on GitHub.com
{%- endif %}
* Interacting with Copilot on a mobile device
* Interacting with Copilot Chat for CLI
The `last_activity_at` date is consistent across the CSV generated via `Get Report` in Copilot Access settings as well as through {% data variables.product.prodname_dotcom %}'s REST API. The events which are tracked come from both client, and server-side telemetry. This allows the timestamp to be durable in the event that network conditions would impact client-telemetry.
## Further reading
{% ifversion ghec%}