Skip to Main Content
Pragmatic Guide to Git
book

Pragmatic Guide to Git

by Travis Swicegood
November 2010
Beginner content levelBeginner
160 pages
2h 50m
English
Pragmatic Bookshelf
Content preview from Pragmatic Guide to Git
22 Sending Changes to Remotes

You have to publish your repository somewhere that is accessible to other members of your team. You send your changes to that repository using the git push command.

Calling git push without any parameters causes Git to assume you want to push all of your local branches that have a matching branch on the origin repository. You can provide both a remote repository and a branch name.

git push takes both named remote repositories (that is, those that have been added via git remote add) and full URLs to remote repositories.

You can provide a branch name to specify which branch to push, but in order to provide a branch, you must specify a remote repository. For example, to push your beta branch to your origin ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Pragmatic Version Control Using Git

Pragmatic Version Control Using Git

Travis Swicegood
Git Version Control Cookbook - Second Edition

Git Version Control Cookbook - Second Edition

Kenneth Geisshirt, Emanuele Zattin(EUR), Aske Olsson, Rasmus Voss
Git for Programmers

Git for Programmers

Jesse Liberty

Publisher Resources

ISBN: 9781680500028Errata