Support Branch-Specific Upstream Settings in Web UI

[uno1982]

Select Topic Area

Product Feedback

Body

Use Case

Working with Unreal Engine forks that track different upstream sources (Epic Games and Meta/Oculus). Currently managing:

• Standard version branches (5.3, 5.4) tracking Epic Games upstream
• Specialized Meta/Oculus branches (4.27.2) tracking Meta's fork
• Each branch needs different comparison and tracking settings

Current Behavior

• GitHub web UI only allows repository-wide upstream settings
• Always compares against original fork source (EpicGames/UnrealEngine:release)
• Local git configuration can track correct upstreams, but this isn't reflected in web UI
• Example: meta-branch-4.27.2-v62.0 correctly tracks MetaFork/4.27 locally but GitHub compares against Epic's release branch names need to be named differently to avoid confusion and conflicts in a fork vs both upstream sources since that upstream likely also tracks the original.

Requested Feature

• Allow setting upstream tracking per branch in web UI
• Maintain these settings for PR comparisons and branch status
• Match local git's ability to track different upstreams for different branches
• Preserve existing default repository upstream for branches without specific settings

Benefits

• Better support for projects tracking multiple vendors/forks
• Accurate branch comparison visualizations
• Reduced confusion for team members using web UI
• Aligns web experience with local git capabilities
• Particularly valuable for game engine development and other large-scale software with vendor-specific forks

Impact

This would benefit:

• Game studios working with multiple engine vendors
• Teams maintaining different versions of forked software
• Projects that sync with multiple upstream sources
• Organizations managing complex fork relationships

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