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
In the .env file, there is an option to connect with a GitHub Personal Access Token:
VUE_APP_GITHUB_TOKEN=
In large organizations, there are policies against over granting privileges to tokens for sensitive things like copilot billing and usage. Following the principle of least privilege, we are required to access sensitive data via a GitHub app.
Support for connecting through a GitHub app would allow us to use this project as is. For example:
VUE_APP_GITHUB_KEY=<name of the private key file>
VUE_APP_GITHUB_APPLICATION_ID=<application ID>
VUE_APP_GITHUB_INSTALLATION_ID=<installation ID>
A workaround is to extract the data from the GitHub Copilot Usage endpoint, and store it in a file called src/resources/metricsExample.json and set VUE_APP_MOCKED_DATA=true. This would require additional automation, and the preferred way would be to pull real time data from the API with a GitHub App.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion @JackColeman - it makes sense. With the GitHub App approach, it would be possible to fetch Copilot usage metrics for organization and Teams but not for Enterprise members. cc: @djopatrny , for awareness
In the .env file, there is an option to connect with a GitHub Personal Access Token:
VUE_APP_GITHUB_TOKEN=
In large organizations, there are policies against over granting privileges to tokens for sensitive things like copilot billing and usage. Following the principle of least privilege, we are required to access sensitive data via a GitHub app.
Support for connecting through a GitHub app would allow us to use this project as is. For example:
A workaround is to extract the data from the GitHub Copilot Usage endpoint, and store it in a file called
src/resources/metricsExample.json
and setVUE_APP_MOCKED_DATA=true
. This would require additional automation, and the preferred way would be to pull real time data from the API with a GitHub App.The text was updated successfully, but these errors were encountered: