Disabling `Update branch` button
See original GitHub issueThink we can disable this update branch
button (image below) from PR on this repo settings. This button is just adding some noisy to all opened pull requests, because it enforces the branches to be up-to-date with master all the time, and we had to be requesting rebasing/squashes.
Button:
Example of the noisy:
Even when we disable the button, Github will guarantee to use integrity of the code. And also, it will tell us when there’s a conflict between branches, the we can act directly on it before merge. Otherwise, there’s no need to be up-to-date with master all the time.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Protected branches and required status checks
The new “Update branch” button lets you merge the latest changes from the base branch of the Pull Request with one click. Pull...
Read more >"Update" button disabled in GitHub Desktop - Stack Overflow
I learned the answer: You can merge a feature branch back the master branch by switching to the master branch and then click...
Read more >Delete source branch button is disabled after PR completes
Lately when a pull request completes the "Delete source branch" button is always disabled, even though I haven't deleted it yet.
Read more >Remove source branch button should be disable if there are ...
Remove source branch button should be disable if there are new changes on the branch ... An error occurred while loading designs. Please...
Read more >Disable or limit the "Create Branch" option - Jira - Atlassian
Add another permission for Create Branch specifically or provide an option to disable it. Workaround. None. Comments. George Shaw. Added 9/11/ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any update here? I’d like to see the option of enforcing this without the button present. Devs can rebase on their local and push rather than use the button.
@rsp we don’t “disable” the button as you may be thinking, we just remove the check forcing branches to be up-to-date with master. Personally, I prefer to keep this ON, but as @luisfmsouza said, it adds some misunderstanding on novice people and difficult contributions with some kind of
invisible contribute wall
rule!Settings 👇
So far, so good! We had no problems without this option 🙂