Feature Request: Verified Peer-to-Peer Networking & Native Chat via Mutual Follows

[alexemmanuel]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

Right now, GitHub is the ultimate platform for proof-of-work, but developer communication is heavily fragmented. If you spot an incredible contributor or potential partner on an open-source repo, you have to hunt down an external contact link (if one even exists) or jump into messy issue threads.
​Here is a proposal to turn GitHub into a true professional network while keeping spam entirely out of the picture.

​1. The Core Thesis: Verified Peer-to-Peer Networking
​Unlike LinkedIn—where anyone can message anyone (leading to spam) or claim skills they don’t have—GitHub features a built-in trust layer: code. A mutual-follow requirement ensures both parties mutually respect each other's work before a conversation ever starts.

​2. The Problem It Solves
​The "Resume Black Hole": Traditional hiring disconnects great engineers from opportunities through layers of recruiters, HR gatekeepers, and automated resume filters.
​The Fragmented Workflow: Founders and engineering leads who spot incredible talent on a repo are forced to break flow and look off-platform just to start a conversation.

​3. The Value Proposition (Why GitHub Should Care)
​Creates a True Developer Economy: By lowering the friction between technical peers, GitHub directly facilitates hiring, co-founding teams, and freelance collaborations.
​Keeps Developers on Platform: Instead of users migrating conversations immediately to X, Discord, or Telegram, GitHub captures the entire lifecycle of a developer relationship—from code contribution to direct conversation.

​4. Bulletproof Guardrails
​To ensure safety and respect user focus, the system should include:

​Strictly Mutual-Follow: No cold messaging strangers. Both users must follow each other to initiate a chat.

​Opt-In/Opt-Out Toggle: A simple settings switch for developers who want to disable the chat feature entirely and write code in peace.

​Code & Context Sharing: Seamlessly embedding pull requests, issues, or commit links directly inside the chat interface.

​Let's bridge the gap between code and community. Upvote if you'd love to see native, mutual-follow messaging on GitHub!

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