push a remote branch to remote master git

#Push a remote branch to remote master git update
#Push a remote branch to remote master git software

IMHO, a warning that you're about to push to the repository's default GitHub branch would great regardless of the scenario. ❓ Possibly silly question: Forgive me if I'm incorrect, but it looks like you can't set up tracking branches from within Desktop: so, why does Desktop make assumptions on where to push if there is a tracking branch specified and it overrides the default git behavior? In my case, I would like to use both the CLI and Desktop at the same time: I mostly create and push branches from the CLI, but Desktop is great if I need a GUI to view history or write a fancy commit message. 🤔 I can understand this point, but I don't agree on an all-or-nothing approach to assuming Desktop use. Since this doesn't look like a scenario you could get into without going to the command line I'm not going to classify this as a bug and by the looks of how complex this issue is we're not going to be able to spend time on it as part of our current roadmap. Yep, I think it's dangerous to not respect git defaults without at least notifying/warning the user, especially so when it involves pushing to default branches like master.

So I think the problem here is that we don't respect the fault configuration since we explicitly specify the target branch. Recently, I was using Desktop to write some co-authored commit messages (which Desktop makes extremely friendly! 🚀 ), but I accidentally clicked the 'Push' button, and was shocked to see that Desktop pushed my branch's changes to our production master. But with fault set to simple (git's default as of 2.0), I know git push would never allow pushing directly to master without me manually doing it. I usually have my branches track origin/master to easily see how far I am ahead/behind. 👋 I'll add a +1 to this affecting me, too. Info: Executing push: git -c credential.helper= push origin test-push:master -progress Additional information ! test-push -> master (pre-receive hook declined) - luckily the remote master branch is protected, otherwise it would've been updated! Logs The current branch should be pushed to the remote repository, as if I'd run git push. In GitHub Desktop, click 'Push origin'.In GitHub Desktop, check that 'test-push' is showing as the Current Branch.The tracking will be set up by Git during the pushing.

• git checkout -b test-push origin/master To push the local branch to the remote repository, you should run the git push command by specifying the branch name (suppose, the name of remote is origin, which is by default): git push -u origin .

OS version: macOS 10.12.5 Steps to Reproduce If you receive an error you main need to go into the web UI for your git host (Github for instance) and find the setting for 'default branch' and switch it to main before deleting the old master branch.After branching off origin/master and committing some changes to the new branch, 'Push origin' pushes the commits to the remote master branch, instead of just pushing the current branch to a remote branch with the same name (as git push would do). Git branch -m master main Step 2 - Rename Remote Branch git checkout main

#Push a remote branch to remote master git update

If you'd like to update any existing repos to use main as the new default branch name, just follow these steps: Step 1 - Rename Local Branch

#Push a remote branch to remote master git software

If you are running into this error in any part of your software infrastructure, or suspect this change of github default branch name is causing an issue in your application, please get in touch and we'll help you solve the issue. So instead of pulling from the master branch, moving forward we'll pull from the default main branch: The default git branch name master has recently been found to be racist, so it's been changed to default to main instead. It's probably because you have tried to use the old racist command: If you encounter the following error on a recently created github project when trying to pull from the default branch: