Provide separate settings for default view branch vs. default PR base branch #5705
Replies: 2 comments
-
I found this discussion after being directed here from isaacs/github#1401, where there was much more engagement with the issue: I imagine this is a feature that would be leveraged by a high percentage of repositories. We want other developers to see what code is live, which is the master/main branch. However, defaulting to PR-ing into the development branch is preferred given the reasons @kfranqueiro listed. 100x BUMP this! |
Beta Was this translation helpful? Give feedback.
-
I'm curious why this issue hasn't gained more traction. The issue @rmi22186 mentions has been archived, and this one seems largely ignored :( |
Beta Was this translation helpful? Give feedback.
-
Often, in GitFlow-style setups, the main branch (which most users are encouraged to use) is separate from the development branch users are encouraged to make PRs to.
Having the option to make a different branch from main be the default PR branch would be excellent.
Additionally, I'd like to see an option to prevent outside pull requests to certain branches. For example, a fork's pull request can only be made towards my develop branch, but my develop branch can go to master.
Beta Was this translation helpful? Give feedback.
All reactions