Publishing a Local Repository on a Remote [Learn Git Video Course] скачать в хорошем качестве

Publishing a Local Repository on a Remote [Learn Git Video Course]

Learn how you can publish a local repository on a remote server for the first time. This video is part of our free 24-part video course on Learning Git on the Command Line. Subscribe ►    / @gittower   *************************************** Additional Git tutorials and resources Learn Git on the Command Line: a free 24-part video course ►    • What is Version Control? [Learn Git Video ...   Learn Git with Tower:    • Learn Git with Tower   Surviving with Git:    • Surviving with Git   More Productive in Git with Tower:    • More Productive in Git with Tower   *************************************** Welcome to our video series on learning version control with Git. Today, we'll publish a local repository on a remote server. Let's talk a bit about the situation first. You created a new Git repository for your project on your computer. You've worked a bit in this new repository and now want to start sharing it with other people. That's when you create a new, empty remote repository on a server. This could be any of the popular hosting services like GitHub, Beanstalk, or Bitbucket - or maybe your company's own server. Now's the time to publish your project. We'll connect your local Git repository with that new and empty remote one. And we'll then publish your work for the first time on the server. After this, your teammates can then clone a copy of the project to their computers - and you can all start collaborating. Let's go! First, you have to quickly connect that new remote repository. With "git remote add", a handy short name, and the repository URL. Now we're ready to publish our local repository on the server. The "git push" command is what we need. We'll talk about this command in detail in a later video - including that "u" flag here. The first important parameter is this: which remote repository do you want to push to? Since we've just connected a remote and named it "origin", we'll upload our project there. The second important information is: to which branch on that remote do we want to push? Here in our local repository, we're currently on the "master" branch. It makes sense to keep names consistent between the local and the remote repository. Therefore, and since the remote repository is still empty, this command will create a new remote branch with the same name. And this is it - we're uploading all of the commits from our local master branch to the remote repository. SUBSCRIBE to learn more about Git, Tower, and how to become a better developer!    / @gittower   For more free ebooks, cheat sheets, and video tutorials make sure to check out our FREE learning platform! https://www.git-tower.com/learn/ STAY UP-TO-DATE: Tower: https://www.git-tower.com YouTube:    / @gittower   Twitter:   / gittower   Facebook:   / gittower   #git #learngit #gittutorial