#GIT TUTORIAL INSTALL#
#GIT TUTORIAL FULL#
#GIT TUTORIAL SOFTWARE#
#GIT TUTORIAL CODE#
#GIT TUTORIAL DOWNLOAD#

You should see output indicating that 1 file has changed and a new mode was created for readme.txt ( Figure 4 ).įigure 4: Our commit was successful. For example, since this is the first commit for the readme.txt file, the commit could be: git commit -m “First draft of readme.txt file” Where Descriptive Message is your message about the changes within the commit.

Now we can create the commit by issuing the command: git commit -m “Descriptive Message”

#GIT TUTORIAL FULL#

Where EMAIL is your email address and FULL NAME is your name. To do this, issue the command: git config -global user.email EMAIL git config -global user.name “FULL NAME” Before we do this, however, we have to inform Git who we are.

By doing this, you are adding notes about what the commit contains (such as what changes you’ve made to the file). It is important, however, that you include a descriptive message for the commit. Creating the commit is actually quite simple. What is a commit? Easy: A commit is a record of the files you’ve changed within the project. With the new file in the staging environment, you are now ready to create your first commit. Once you’ve done that, issue the git status command again to see that readme.txt is now considered a new file in the project ( Figure 3 ).įigure 3: Our file now has now been added to the staging environment. To do that, issue the command: git add readme.txt Issue the command git status to verify that Git is aware of the new file ( Figure 2 ).įigure 2: Git knows about our readme.txt file.Įven though Git is aware of the file, it hasn’t actually been added to the project. You will now have an empty file in your repository. From within the root folder (~/newproject) issue the command: touch readme.txt Next we need to add a file to the project. When the command completes, you should see that the empty Git repository has been created ( Figure 1 ).įigure 1: Our new repository has been initialized. In the ~/newproject folder, issue the command git init. Open up a terminal window and issue the commands: cd ~/ mkdir newproject cd newproject The next step is to create a local repository on your system (we’ll call it newproject and house it in ~/). Where ADDRESS is the URL given on the software’s Git page.ĭoing this most always ensures I am installing the latest release of a package. Instead of downloading the source files from a third-party location, I’ll often go the project’s Git page and clone the package like so: git clone ADDRESS

#GIT TUTORIAL SOFTWARE#

There are times when a piece of software isn’t available via the built-in package manager.

#GIT TUTORIAL DOWNLOAD#

On a side note: I use Git quite a bit to download source for application installation. This will include a rather large number of dependencies, but you’ll wind up with everything you need to work with Git and GitHub.

#GIT TUTORIAL INSTALL#

Open up a terminal window and issue the command: sudo apt install git-all Once you’ve done that, you’re ready to move on to installing Git (you can actually do these two steps in any order). Head over to the GitHub signup page and fill out the necessary information. The first thing to do is create a free GitHub account. I’ll be demonstrating on Ubuntu 18.04, so if your distribution of choice is different, you’ll only need to modify the Git install commands to suit your distribution’s package manager. I will walk you through the very basics of getting Git up and running and using it with GitHub, so the development on your game-changing app can be taken to the next level. Along with Git comes a handy repository called GitHub, where you can house your projects, such that a team can check out and check in code. With such a system, collaborating on a project becomes incredibly efficient and reliable.

#GIT TUTORIAL CODE#

You code as if your mind and your fingers are one to create elegant, perfectly commented, source for an app you know will take the world by storm.īut what happens when you’re tasked with collaborating on a project? Or what about when that app you’ve developed becomes bigger than just you? What’s the next step? If you want to successfully collaborate with other developers, you’ll want to make use of a distributed version control system. You can develop with GUI tools or from the command line. You’ve spent years studying one or more programming languages and have perfected your skills. If you’re a developer, then you know your way around development tools.

Git tutorial