Improve PullShark to show up-to-date complete pull-request summary

[DRNadler]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Profile

Body

I think the way Pull Shark history works is causing a lot of confusion and complaints.
Consider this use case...

A hiring manager or someone evaluating a potential contributor sees Pull Shark, and looks at the detail/history.
But the history only shows some of the person's contributions, which is misleading. Because the Contribution display is way too granular where people need a summary (as in this use case), they can't use it.

Many of us don't care whether its a Pull Shark 'x2' badge or whatever, and don't care about the thresholds.
But it would be better for everybody if the detail/history under Pull Shark was complete!

Consider someone looking at my profile on github in the above use case:
https://github.com/DRNadler?achievement=pull-shark&tab=achievements
They see a couple contributions. They don't see these at all:

• https://github.com/LiorKogan/Circular/pulls?q=is%3Apr+is%3Aclosed+author%3ADRNadler
• Add uxTaskCallForEachTask, and refactor uxTaskGetSystemState to use it. FreeRTOS/FreeRTOS-Kernel#1439

The pullshark summary for this repository only shows 16 merged pull requests, but there are 45:

• https://github.com/GitHubLionel/wxMathPlot/issues?q=is%3Apr%20author%3ADRNadler

So the viewer does not see high numbers, they don't see a contribution to a real operating system, nor contributions to a math library. They are not going to troll through a decade of contributions.

Please consider improving the Pull Shark history/detail display, as it continues to cause complaints and confusion!
Thanks!
Best Regards, Dave

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐