-
Notifications
You must be signed in to change notification settings - Fork 312
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
Improve readibility of compare_to_baseline output message #2025
Conversation
This pull request was exported from Phabricator. Differential Revision: D51632256 |
) Summary: Integrating the following feedback into the construction of the compare_to_baseline output message " I'm noticing this could be a bit easier to digest. Luckily we can use markdown formatting as follows: * add an asterisk before each item in comparison_list so that the user gets a bulleted list. * put metric name + percent improvement first, followed by arm names + absolute metric values, since the former tends to be what the user most cares about. * bolding the first part of each line item can help create visual anchors for the reader. * adding backticks can help users identify variable names/values. " Differential Revision: D51632256
7b23d40
to
639c487
Compare
This pull request was exported from Phabricator. Differential Revision: D51632256 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2025 +/- ##
=======================================
Coverage 94.47% 94.47%
=======================================
Files 460 460
Lines 44335 44335
=======================================
Hits 41885 41885
Misses 2450 2450 ☔ View full report in Codecov by Sentry. |
) Summary: Integrating the following feedback into the construction of the compare_to_baseline output message " I'm noticing this could be a bit easier to digest. Luckily we can use markdown formatting as follows: * add an asterisk before each item in comparison_list so that the user gets a bulleted list. * put metric name + percent improvement first, followed by arm names + absolute metric values, since the former tends to be what the user most cares about. * bolding the first part of each line item can help create visual anchors for the reader. * adding backticks can help users identify variable names/values. " Reviewed By: bernardbeckerman, mpolson64 Differential Revision: D51632256
639c487
to
de9bd5d
Compare
This pull request was exported from Phabricator. Differential Revision: D51632256 |
) Summary: Integrating the following feedback into the construction of the compare_to_baseline output message " I'm noticing this could be a bit easier to digest. Luckily we can use markdown formatting as follows: * add an asterisk before each item in comparison_list so that the user gets a bulleted list. * put metric name + percent improvement first, followed by arm names + absolute metric values, since the former tends to be what the user most cares about. * bolding the first part of each line item can help create visual anchors for the reader. * adding backticks can help users identify variable names/values. " Reviewed By: bernardbeckerman, mpolson64 Differential Revision: D51632256
de9bd5d
to
a345835
Compare
This pull request was exported from Phabricator. Differential Revision: D51632256 |
This pull request has been merged in ef948b3. |
Summary:
Integrating the following feedback into the construction of the compare_to_baseline output message
" I'm noticing this could be a bit easier to digest. Luckily we can use markdown formatting as follows:
Differential Revision: D51632256