And it’s used not just as a version control system, but also as a means of cloning repositories to your desktop or server, so you can then install whatever application is found in that repository. Although you might not need to know about Git during your first steps with Linux (or as a developer), at some point you will. I’ve even found I can use Git and GitHub for documents and other types of files, not just code. Let me walk you through those first steps. Also: C++ programming language and safety: Here’s where it goes next
Requirements
I’m going to demonstrate Git on the Ubuntu-based Pop!_OS Linux. You don’t have to be using that particular distribution but if you’re using a version of Linux that’s not based on either Ubuntu or Debian, you’ll need to alter the installation command from using apt to the package manager of choice for your distribution (such as dnf for RHEL-based distributions). You’ll also need a user with sudo privileges. That’s it. Let’s take our first steps with Git.
How to get started with Git on Linux
Install Git
Create a local repository
That’s all there is to initializing your first repository.
Adding files to your repository
From the project directory, create a README text file with the command: In that file, you can add any information you want to give other developers or users. Once you’ve finished, save the file with the CTRL+X keyboard shortcut. After you add the file to the repository, Git will automatically notice the file but can’t do anything with it. To allow Git to use the file, you must add what is called a commit. A commit is an operation that sends the latest changes made to the source code to the repository. In other words, if you don’t make a commit, Git will not be aware of any changes. In our case, Git won’t be aware that the newly added file contains any information. To make it aware, we’ll use the git add command like so: If you’ve created more than one file in the repository, you can add them all at once with the command: You can check the status of the repository with the command: The output to the above command will look something like this: We now have changes that must be committed. The next step is to create a commit for our newly added README.txt file. When you create a commit, you add information to it so that anyone else working on the project knows what has been done. For example, we just added the README.txt file, so we’ll want to create a commit to indicate that very thing. A git commit looks something like this: The output of the above command will look something like this: If you issue the git status command, you should see output similar to this:
Pushing your commits
This next step in the process requires that you have a GitHub account. You will also have to have created an access token, which is done in GitHub Settings > Developer Settings > Personal Access Tokens. Once you’ve created a Personal Access Token, make sure to copy it, as you cannot view it again without regenerating it. To finally make those changes available, we push them with the command: You’ll be asked for your GitHub username and password (which is the Personal Access Token you just created). Once you successfully authenticate to your GitHub account, you should see something like this in the output: Where USERNAME is your GitHub username. Also, if you log in to your GitHub account, you’ll see that a new repository has been created that includes all of the files in your local repository. At this point you can add new files or edit existing files from GitHub in your web browser. If you do that, you can then pull down those changes to your local repository, with the command: Any file that you added to the GitHub repository will be pulled down and available to your local repository for editing. And that’s the gist of the basic Git workflow. Although it might seem a bit cumbersome at first, once you get the hang of it, you’ll find it to be considerably easier than you think.
