Essentially creating a timeline of versions of a project as it progresses, so that you can roll back to an earlier version in the event disaster strikes.
Master git code#
Or at least not disastrous.īy now you understand that git saves each version of your project as a snapshot of the code exactly as it was at the moment you committed it. Now it is time to start actually working with GitHub (and git) the way they are meant to be used: making changes in the project safely off to one side, and merging them back into the original project once they have proved to be correct.
Master git how to#
They are just part of a naming convention that Git follows.In our previous tutorials for the git version control software, we learned the essential basic commands for using git, as well as how to work with to establish a repository and push our project code to the website. Both of these names can be changed by the user and have nothing special about them. Master is the default name given to the first branch present in a Git repository when it is initialized. Origin is the remote repository from where we cloned our local repository and we will be pushing and pulling changes to it. Origin and master are just two default names used commonly by Git. And now the remote repository will be the origin of our local repository. We will also have a remote-tracking branch called origin/master that will track the changes in the remote master branch. Now, if we clone this repository to our local system, then we will get a local master branch with all three commits. Suppose we have a remote repository with just a single branch called master with three commits on it. Now that we know about the general terminology, let's see what actually happens when we clone a repository.
Now, we can run the Git Branch command and see that we only have a single branch in our repository which is called the master. We will create an empty commit because a branch is just a pointer to a commit, and we will need one to view the master branch(the branch name is also visible in blue color next to the path of our directory). This name is just used to denote that it is the main branch of our repository.Ĭonsider the following example where we initialize a new Git repository. Again, there is nothing exceptional about this name, and we can rename our master branch to something else.All other branches will be created based on some commit of this branch and will eventually merge into the master branch. This branch will have the final, up-to-date, production-ready code.When a new Git repository is initialized using the Git Init command, it will only have a single branch and that branch, by default, is called the master.Master is the default name that Git gives to a branch when we create a new repository.We can also change this default name with the help of the Git Remote Rename command. We can see in the image below that we have a remote called origin. Next, we are going to check the remotes present by using the Git Remote command. First, we will run the Git Clone command, and pass the URL for the remote repository. There is nothing extraordinary about this word and we can use any other name that we like.Ĭonsider the example below where we try to clone a remote repository to our local system. It is a standard default name given to the repository from where our local repository originated.This name will be used in the future when we have to push or pull changes from the remote repository. In Git terminology, the origin is the name given to the remote repository from where we clone our local repository. This same definition can be applied to the word origin which is used in Git.Origin, in simple terms, is described as the place from where something begins or is derived.Let's learn more about origin and master, and see how they are used. Origin is the default name given to a remote repository, and master is simply a branch name. Origin and master are two terms frequently used when working on a project managed using Git.
0 kommentar(er)
