Adding the name of the "branch to push"- amd_qlp_tester-(1) shuts it up, and (2) pushes just that one branch. So now (depending on your version of git and whether you've configured things in detail), git may print a lot of warnings about defaults changing in the future.
The issue with these is that people have changed their minds, over time, as to what is "reasonable". The URL is whatever you cloned from and the rest, if set or unset, are all "reasonable" defaults. When you first cloned the repo-whenever that was-git set up default values for some of these. what gets fetched when you run git fetch remote.what gets pushed, if you didn't say what branch(es) to push.where (URL-wise) that remote "lives" (e.g., ssh:// hostname/ path).git/config file to find the named "remote" (e.g., origin). The command git push remote roots around in your. In your case, Petr Mensik's answer is the (well, "a") right one.
#Git create branch on origin how to
Which is great, if you know what you want and how to spell that in Git-Ese, but you're new to git! :-) The answers in question you linked-to are all about configuring git so that you can enter very short git push commands and have them do whatever you want. So, in the first part of command you will tell Git where to find repository for this project, and then you just specify a branch. git/config file, you will see an entry which specifies url of the repository. Syntax of push looks like this - git push. If you just type git push, then the remote of the current branch is the default value. Git push origin amd_qlp_tester will work for you. When your local and remote branch name is different then you can just do it: git push origin localBranchName:remoteBranchName If your Local branch and remote branch is the same name then you can just do it: git push origin branchName
0 kommentar(er)
