Return to Answer

origin is an alias on your system for a particular remote repository. It's not actually a property of that repository.

By doing

git push origin branchname

you're saying to push to the origin repository. There's no requirement to name the remote repository origin: in fact the same repository could have a different alias for another developer.

Remotes are simply an alias that store the url of repositories. You can see what url belongs to each remote by using

git remote -v  

In the push command, you can use remotes or you can simply use a url directly. An example that uses the url

git push [email protected]:git/git.git master

origin is an alias on your system for a particular remote repository. It's not actually a property of that repository.

By doing

git push origin branchname

you're saying to push to the origin repository. There's no requirement to name the remote repository origin: in fact the same repository could have a different alias for another developer.

Remotes are simply an alias that store the URL of repositories. You can see what URL belongs to each remote by using

git remote -v

In the push command, you can use remotes or you can simply use a URL directly. An example that uses the URL:

git push [email protected]:git/git.git master

origin is an alias on your system for a particular remote repository. It's not actually a property of that repository.

By doing

git push origin branchname

you're saying to push to the origin repository. There's no requirement to name the remote repository origin: in fact the same repository could be have a different alias for another developer.

Remotes are simply an alias that store the url of repositories. You can see what url belongs to each remote by using

git remote -v  

In the push command, you can use remotes or you can simply use a url directly. An example that uses the url

git push [email protected]:git/git.git master

origin is an alias on your system for a particular remote repository. It's not actually a property of that repository.

By doing

git push origin branchname

you're saying to push to the origin repository. There's no requirement to name the remote repository origin: in fact the same repository could have a different alias for another developer.

Remotes are simply an alias that store the url of repositories. You can see what url belongs to each remote by using

git remote -v  

In the push command, you can use remotes or you can simply use a url directly. An example that uses the url

git push [email protected]:git/git.git master

origin is the original remote repository, by convention it is the 'primary' centralized repository as well.

By saying git push origin branchname you're saying to push to the origin repository. There's no requirement to name the remote repository origin, and there can be multiple remote repositories.

Remotes are simply an alias that store the url of repositories. You can see what url belongs to each remote by using git remote -v.

In the push command you can use remotes or you can simply use a url directly. An example that uses the url: git push [email protected]:git/git.git master

origin is an alias on your system for a particular remote repository. It's not actually a property of that repository.

By doing

git push origin branchname

you're saying to push to the origin repository. There's no requirement to name the remote repository origin: in fact the same repository could be have a different alias for another developer.

Remotes are simply an alias that store the url of repositories. You can see what url belongs to each remote by using

git remote -v  

In the push command, you can use remotes or you can simply use a url directly. An example that uses the url

git push [email protected]:git/git.git master