Add a “Clones by Country” graph to GitHub Insights (with toggleable list/graph view)

[laurentbarraud]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

As a maintainer, I regularly check the Traffic section of GitHub Insights to understand how developers interact with my repositories.
The existing graphs (Views, Unique Visitors, Clones, Unique Cloners) are extremely helpful, but they lack one key dimension: geographical distribution.

I suggest adding a fifth graph to the Traffic dashboard, positioned after Clones and Unique Cloners, called “Clones by Country”.

This graph would display:

• the date of each clone
• the country it originated from
• aggregated counts per country over the selected period

This would help maintainers understand where their projects are gaining traction, which communities are engaging with their work, and how international interest evolves over time.

Why this is useful for the community

• Maintainers could better understand their global audience.
• Open‑source contributors could identify regions where documentation or localization might be valuable.
• Developers could track whether outreach efforts (blog posts, tutorials, conference talks) have impact in specific regions.

To make the feature flexible, a simple toggle could switch between:

Graph view (bar chart or line chart)
and
List view (chronological table with date + country + clone count)

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