Skip to content
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

Feature: feedback - contributor graph should default to "enhance" #3863

Closed
jpmcb opened this issue Aug 5, 2024 · 3 comments · Fixed by #3880
Closed

Feature: feedback - contributor graph should default to "enhance" #3863

jpmcb opened this issue Aug 5, 2024 · 3 comments · Fixed by #3880

Comments

@jpmcb
Copy link
Member

jpmcb commented Aug 5, 2024

Suggested solution

The contributor graph, especially for very large projects, can be a pretty poor experience by default:

Screenshot 2024-08-05 at 5 13 49 PM

This is difficult to see the nuance of each individual contributor besides the people who are commiting massive amounts of code.

We've gotten feedback that the "enhanced" view is always clicked and that there is little value in the graph outside of the enhanced view:

Screenshot 2024-08-05 at 5 15 00 PM


We should consider, as a quick win, having the "enhance" toggle on by default.

Copy link
Contributor

github-actions bot commented Aug 5, 2024

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue.

For full info on how to contribute, please check out our contributors guide.

Copy link
Contributor

open-sauced bot commented Aug 7, 2024

🎉 This issue has been resolved in version 2.52.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link
Contributor

open-sauced bot commented Aug 9, 2024

🎉 This issue has been resolved in version 2.52.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@open-sauced open-sauced bot added the released label Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants