However, there are some cases where you might want to explicitly use git push origin: If the original git configurations are being used, git push assumes the current branch is the one to push, and assumes that remote is origin. Git push and git push origin will both push the current branch to the remote counterpart. ![]() NOTE: The behavior described is for git versions 1.7.11 or higher. When should I use git push origin vs git push? This is common when you are the only contributor to your project, and you want to directly edit the default branch of your project with changes. Where git push initiates the push, origin refers to the remote counterpart of the project, and main is the branch name. Pushing to the default branch can be done using: It’s important to check the name of the default branch. If a project you are working on is older, the default branch might be named “master”, which GitHub changed to remove references to slavery in conventional terminology. This branch is the version of the project that goes into production or the version from which you will create further branches to isolate changes, and merge back into the default branch. The default branch in your project is conventionally a branch named “main”. ![]() Git push origin will push the current branch to the branch of the matching name in the remote repository (aka, “branch configured upstream”), if it exists, otherwise, it will not push and notify that the current branch has no remote counterpart (error message: “ has no upstream branch”). Git push origin will push the current branch to the remote counterpart of that branch. You can choose which branch(es) to push to origin: Choosing which branches to git push origin Origin is the conventional shorthand name of the url for the remote repository (usually in GitHub or another cloud git repository provider) for your project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |