UX Issue: Inefficient Navigation Across Long Inactivity Periods in Contribution Timeline

[gleon99]

Select Topic Area

Product Feedback

Body

UX Issue: Inefficient Navigation Across Long Inactivity Periods in Contribution Timeline

Description
When a user has several consecutive months with no activity, the contributions timeline becomes extremely cumbersome to navigate.
To reach the most recent month with activity, one must repeatedly click “Show more activity” month by month, even when those months contain no data.

This forces unnecessary manual interaction and significantly degrades usability, especially for profiles with long inactive periods.

Current Behavior

• Each inactive month must be expanded individually
• There is no way to jump directly to the last month with actual activity
• The number of required clicks grows linearly with the length of the inactivity gap

Expected / Desired Behavior

• Ability to skip contiguous inactive months in a single action
• Or automatically collapse empty months and jump to the next month with activity
• At minimum: a “Jump to last active month” option

Impact

• Poor user experience for reviewers, recruiters, and maintainers
• Makes profile exploration unnecessarily time-consuming
• Disproportionately affects long-standing accounts with sporadic activity

Reproducible Example

• Profile with a long inactivity gap:
  https://github.com/rav872

Priority Justification
This is a core UX issue affecting profile navigation and discoverability.
The impact increases with account age and inactivity duration, making the problem more severe over time.

[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. ⭐