Instrumentation for Blame file information
Proposal
Add instrumentation/analytics around blame information.
From sync meeting from Jan 24, 2024
The assumption is that the blame information in the file page is that it is an easier and faster way to access blame information. You could get a link to the blob page with the blame information. The idea would be to sunset the blame page eventually if users are using it and liking it
Things to track
Goal - Get baseline counts of usage of Blame and related actions:
- Branch dropdown
-
Blame
andHistory
buttons above the commit info -
Blame (Display blame info)
button - Inline blame icon (link to blame page)
-
View blame prior to this change
icon button
Events:
click_blame_control_on_blob_page
click_chunk_blame_on_blob_page
click_history_control_on_blob_page
click_ref_selector_on_blob_page
open_blame_viewer_on_blob_page
click_previous_blame_on_blob_page
Metrics:
- Monthly count of unique users who changed Git revision on Blob page
- Monthly count of unique users who navigated from Blob to Blame page
- Monthly count of unique users who navigated from Blob to Commits page
- Monthly count of unique users who viewed in-file Blame on Blob page
- Monthly count of unique users who navigated from specific line of code to its Blame page
- Monthly count of unique users who navigated from in-file Blame viewer to see prior changes on Blame page
To be handled separately in page analytics platform:
- Page views of existing Blame page
- Incoming pages top 20
- Outgoing pages top 20
Resources
Edited by Paulina Sedlak-Jakubowska