-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show the Acceptance Rate (by count) and Acceptance Rate (by lines) #113
Comments
would it make sense to update to new API first? |
DevOps-zhuang
added a commit
to DevOps-zhuang/copilot-metrics-viewer
that referenced
this issue
Nov 20, 2024
Related to github-copilot-resources#113 --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/github-copilot-resources/copilot-metrics-viewer/issues/113?shareId=XXXX-XXXX-XXXX-XXXX).
will update it to latest metrics route API once it is with high data quality. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the current Acceptance rate is calcuated by (lines_accepted/ lines_suggested) * 100. it ingore the accepted count.
so we got some customer's feedback, that it is better to calcualte the (total_acceptances_count/total_suggestions_count)*100.
and In order to keep the version compatible, it is better to keep both. that's to say, show both the Acceptance Rate (by count) and Acceptance Rate (by lines).
1, It needs to edit both the Languages and breakdown page. show both Acceptance Rate (by count) and Acceptance Rate (by lines) there. and for the table, it is better to add more columns, currently, there is 4 columns, which are Lanuage Name/Accepted prompts/Accepted lines of Code/Acceptane Rate (%) , it is better to be Lanuage Name/Accepted prompts/Sugged Prompts/Accepted lines of Code/Suggested Lines of Code/ Acceptane Rate by count (%) /Acceptance Rate by Lines (%)
2, for the Acceptance rate (%), in Main page, update it to 'Acceptance rate by lines (%)' to make it more easy to be understood.
The text was updated successfully, but these errors were encountered: