From the course: Coding Exercises: Git
Unlock the full course today
Join today to access over 24,800 courses taught by industry experts.
Managing multiple remotes - Git Tutorial
From the course: Coding Exercises: Git
Managing multiple remotes
(electronic computer game music) - Sometimes it's good to be able to send your work to more than one location, but how do you manage to send changes to more than one repos? I'll give you a couple of seconds to think about how you'd something like this. (electronic music) Now the answer is understanding remotes. You're probably used to adding your remote when you first open a project, by issuing a git remote and then add, then plus a name that's usually origin, whenever you get started, and then you use a URL right here. Now there's a number of other commands that you can use in addition to this. So you can change of course the name to something like "working" if you're working with a specific project, and then add another remote. You can just push to more than one place if you want to. Now, you can also remove an existing origin and also do things like "get-url" and also for example, get or change the URL of a…
Contents
-
-
-
Cloning with limited history1m 33s
-
(Locked)
Adding to a previous commit4m 36s
-
(Locked)
Identifying your changes2m 26s
-
(Locked)
Managing multiple remotes2m 42s
-
(Locked)
Cleaner logs3m 25s
-
(Locked)
Using Git to hunt down bugs5m 7s
-
(Locked)
Working on multiple branches3m 19s
-
(Locked)
Creating a .zip file2m 57s
-
(Locked)
Getting rid of quick fixes4m 48s
-
(Locked)
Marking items without branching4m 8s
-
(Locked)
Removing untracked files2m 44s
-
(Locked)
Renaming branches2m 31s
-
(Locked)
Remove local, keep master3m 15s
-
(Locked)
Picking specific commits4m 30s
-
(Locked)
Creating a safety net for fixes2m 51s
-