Enhancing Copilot usage API with repo URLs #112377
Unanswered
ghfrontierman
asked this question in
Copilot
Replies: 1 comment
-
I think this is the minimum amount of information that we need for Copilot enterprise/organization. I think we will eventually need to have information regarding individual user usage, but I agree that usage per repository is the first step. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
Hello GitHub Team and Community, I have started to evaluate the GitHub Copilot usage REST API available under early access.
After gaining experience with this API over an extended period, I began wondering how to correlate individual Git repos with the usage data points that this API returns.
This got me wondering if the breakdown structure could be shaped to include the 'repository' as part of the json response. Possibly a response that might include the git remote URL, something like this example:
"breakdown": [
{
"repository": "https://github.com/myproject/mysvc.git",
"language": "python",
"editor": "vscode",
"suggestions_count": 300,
"acceptances_count": 200,
"lines_suggested": 600,
"lines_accepted": 300,
"active_users": 3
},
..
..
Including the 'repository' field would further enhance the utility of the data by allowing users to correlate Copilot's usage metrics with specific Git repos directly.
I would like to hear feedback from GitHub and the community on this suggestion and whether it aligns with the vision for the Copilot usage API. Thank you for considering my feedback.
Beta Was this translation helpful? Give feedback.
All reactions