GitHub Community
Disable "had recent pushes" banner for some branches #35200
Replies: 119 comments 16 replies
-
|
I vote for this change |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
-
|
I agree with this. Or when I PR and merge into one branch, between the two they still say there's a difference, and when it shows the difference, it's comparing with a previous commit. Am I missing something? |
Beta Was this translation helpful? Give feedback.
-
|
I had this also, in my case one of them had a merge commit and the other not. It's able to merge but will not do much. |
Beta Was this translation helpful? Give feedback.
-
|
This would sort both issues. If |
Beta Was this translation helpful? Give feedback.
-
|
That would be awesome, kinda annoying when your main branch is develop and you push something to "main" |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I'm interested in Dev Branch Composing. |
Beta Was this translation helpful? Give feedback.
-
|
Just ran into this suggestion. I was surprised this is not an option in branch protection rules. |
Beta Was this translation helpful? Give feedback.
-
|
Yep same here! |
Beta Was this translation helpful? Give feedback.
-
|
Has there been any movement on this? I also think this would be a great feature especially for branches that have automatic processes occurring on them. |
Beta Was this translation helpful? Give feedback.
-
|
I have a GitHub action that updates data in a separate branch and its a pain to see this every time I log in. |
Beta Was this translation helpful? Give feedback.
-
|
+1 would like to see that too. |
Beta Was this translation helpful? Give feedback.
-
|
I agree this is a pain for the common "develop" > "staging" > "master" branch workflow where the active branch is the "develop" one. This situation is quite common. |
Beta Was this translation helpful? Give feedback.
-
|
No need to go that far with customization. It also happens for the vanilla |
Beta Was this translation helpful? Give feedback.
-
|
This is also unhelpful for orphan branches that shouldn't merge back into the default/main/master/trunk |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I have code that is completely separate from the main branch that does something completely different that I still want in the same repo but not alongside the main code |
Beta Was this translation helpful? Give feedback.
-
|
+1 would be great to see |
Beta Was this translation helpful? Give feedback.
-
|
+1 This is annoying me a bit since I have an automatically managed branch that nobody needs to see any notification about. |
Beta Was this translation helpful? Give feedback.
-
|
+1 please |
Beta Was this translation helpful? Give feedback.
-
|
+100 this is monumental pain. |
Beta Was this translation helpful? Give feedback.
-
|
My suggestion is to add an option during branch protection to ensure that a specific branch is never selected as the source side of a Pull Request. This would be especially useful in scenarios where branches like develop are merged into master or main, but never merged back. In these cases, setting the develop branch as the default and displaying it on the main page can be beneficial, while also providing an extra layer of protection to prevent new Pull Requests from accidentally targeting the master branch. Additionally, the banner suggesting that master needs to be merged back into develop should not appear in this scenario, making the workflow smoother. |
Beta Was this translation helpful? Give feedback.
-
|
+1 from 2024 September |
Beta Was this translation helpful? Give feedback.
-
|
Why is this still not a thing after 2 years and 5 days 😭 |
Beta Was this translation helpful? Give feedback.
-
They forgot to show this page to Bill Gates. |
Beta Was this translation helpful? Give feedback.
-
|
Github wake up |
Beta Was this translation helpful? Give feedback.
-
|
Response #3 |
Beta Was this translation helpful? Give feedback.
and others
-
When protecting branches it should be possible to specify a branch to never be treated as a source (compare) side of a Pull Request.
This is a common scenario where
developis merged intomasterormain, at the end of a change, to trigger specific CD release workflows, and changes are never merged frommasterintodevelop.Declaring the
developbranch instead ofmasteras the default branch is useful. GitHub shows the content of this branch on the repository page, and it prevents new Pull Request from accidentally targeting themasterbranch.The problem with this approach is this banner that makes it easy to think
masterneeds merging back intodevelop. The only difference between the two branches is the merge commit generated by the pull request.Please make it possible to disable this banner for selected branches.
Beta Was this translation helpful? Give feedback.
All reactions