In this guide, I'll walk you through the process of installing and configuring Git on Debian 12 in a few steps.<\/p>\n
![\"Install](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/How-To-Install-Git-on-Debian-12-and-Use-it-Blog-1.png\")
<\/p>\n
Prerequisites<\/h2>\n
Before you install Git, you need:<\/p>\n
- \n
- A Debian 12 server. Get your VPS hosting from a reputable and trustworthy provider like SSD Nodes<\/strong>. We offer powerful Debian servers and the best deals. Take a look at our offerings<\/a> and prepare for your mind to be blown \ud83e\udd2f.<\/li>\n<\/ul>\n
Check out our How to access your server using SSH<\/a> guide to learn how to access your server and create a
sudo<\/code> user.<\/p>\nStep 1: Updating the System Package List<\/h2>\n
Start by updating the packages in the package manager cache to the latest available versions using the following command:<\/p>\n
sudo apt update<\/code><\/pre>\nStep 2: Install Git on Debian 12<\/h2>\n
Debian offers two primary ways to install Git:<\/p>\n
- \n
- Through the APT package manager, which is simpler and faster.<\/li>\n
- Compiling Git from source (which provides more control over the version you install). We'll cover both methods below.<\/li>\n<\/ol>\n
Install Git Using APT<\/strong><\/h3>\n
The easiest way to install Git on Debian 12 is by using the APT package manager. This method installs a stable version of Git directly from Debian\u2019s official repositories. Here\u2019s how to do it:<\/p>\n
sudo apt install git<\/code><\/pre>\nOnce the installation is complete, you can verify the version of Git installed by running:<\/p>\n
git --version<\/code><\/pre>\nOutput:<\/p>\n
git version 2.39.5<\/code><\/pre>\nAt this point, Git should be ready for use. However, if you need a more up-to-date version, you can install Git from source. To do this, follow the instructions outlined in the next section.<\/p>\n
Install Git From Source<\/strong><\/h3>\n
If you need the latest version of Git or want to customize the installation, you can compile Git from source. This method requires a few additional steps, but it allows for greater flexibility.<\/p>\n
First, install the necessary dependencies:<\/p>\n
sudo apt install wget dh-autoreconf libcurl4-gnutls-dev libexpat1-dev \\\r\n gettext libz-dev libssl-dev asciidoc xmlto docbook2x install-info build-essential<\/code><\/pre>\nNext, download the latest Git source code. Visit the\u00a0Git release page<\/a>\u00a0and find the latest version:<\/p>\n
![\"Git](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/git-version-1024x518.webp\")
<\/p>\nNext, use the following command to download and extract it (replace\u00a0
2.47.0<\/code>\u00a0with the latest version number):<\/p>\n\u2022 wget https:\/\/www.kernel.org\/pub\/software\/scm\/git\/git-2.47.0.tar.gz<\/pre>\n
tar -zxf git-2.47.0.tar.gz<\/pre>\n
cd git-2.47.0<\/pre>\n
Now, generate the configuration script for Git:<\/p>\n
make configure<\/code><\/pre>\nOutput:<\/p>\n
GIT_VERSION = 2.47.0\r\n GEN configure<\/code><\/pre>\nRun this configuration script, specifying that the Git binaries should be installed under the
\/usr<\/code> directory:<\/p>\n.\/configure --prefix=\/usr<\/code><\/pre>\nThe output will inform you that the checks are done and the configuration files are created:<\/p>\n
configure: creating .\/config.status\r\nconfig.status: creating config.mak.autogen\r\nconfig.status: executing config.mak.autogen commands<\/code><\/pre>\nCompile Git and build the documentation:<\/p>\n
make all doc info<\/code><\/pre>\nFinally, install Git, along with its documentation:<\/p>\n
sudo make install install-doc install-html install-info<\/code><\/pre>\nVerify that Git was installed successfully:<\/p>\n
git --version<\/code><\/pre>\nYou should see a version that matches the tarball you\u2019ve downloaded:<\/p>\n
git version 2.47.0<\/code><\/pre>\nStep 3: Configuring Git<\/h2>\n
Once Git is installed on your Debian 12 server, the next step is to configure it. This is important because Git needs to associate your commits with your identity. Run the following commands to set up your name and email address:<\/p>\n
git config --global user.name \"Your Name\"\r\ngit config --global user.email \"youremail@example.com\"<\/code><\/pre>\nThese settings will be used in every Git commit you make, so make sure they are accurate. You can verify the configuration at any time by running:<\/p>\n
git config --list<\/code><\/pre>\nStep 4: Using Git<\/h2>\n
Now that Git is installed and configured, it\u2019s time to start using it. Below, we\u2019ll cover some of the most common tasks you'll perform with Git, such as cloning and creating repositories, staging and committing changes, and also managing branches.<\/p>\n
Cloning an Existing Repository<\/h3>\n
If you want to work on an existing project, you can clone its repository. Cloning creates a local copy of the remote repository on your machine, similar to downloading a directory with its files from the web.<\/p>\n
To clone a repository, use:<\/p>\n
git clone https:\/\/github.com\/user\/repo.git<\/code><\/pre>\nThis command downloads the entire repository, including its history.<\/p>\n
Create a New Repository<\/h3>\n
To demonstrate how to use git in a project, create a new directory and navigate to it:<\/p>\n
mkdir myproject\r\ncd myproject<\/code><\/pre>\nThen, run the following command to mark this
myproject<\/code> directory as a Git repository:<\/p>\ngit init<\/code><\/pre>\nThis will create a hidden
.git<\/code> directory, which Git uses to track changes in your project. From here, you can start adding files and making commits.<\/p>\nGit Staging<\/h3>\n
Before committing changes, you need to stage them. Staging allows you to choose which changes should be part of the next commit.<\/p>\n
Changes can be in the form of new files, or modifications to existing files.<\/p>\n
For example, let\u2019s add a new file called
index.html<\/code> to your project:<\/p>\ntouch index.html<\/code><\/pre>\nUse
git status<\/code> to check the status of your Git repository:<\/p>\ngit status<\/code><\/pre>\nThe output will be similar to the following:<\/p>\n
![\"Git](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/Git-Status-1024x271.webp\")
<\/p>\nThis informs you that there is an untracked file called
index.html<\/code> with a helpful message telling you how to make it trackable.<\/p>\nTo add this new
index.html<\/code> to the Git repository and make it trackable, use thegit add<\/code> command:<\/p>\ngit add index.html<\/code><\/pre>\nThis adds the new file to the staging area, meaning Git is now tracking it and will include it in the next commit.<\/p>\n
Check
git status<\/code> again:<\/p>\nOn branch master\r\n\r\nNo commits yet\r\n\r\nChanges to be committed:\r\n (use \"git rm --cached <file>...\" to unstage)\r\n new file: index.html<\/code><\/pre>\nYou can also stage all new files and modifications at once by using:<\/p>\n
git add .<\/code><\/pre>\nThis command adds all modified and untracked files to staging, preparing them for the next commit.<\/p>\n
Committing Changes<\/h3>\n
Once your changes are staged, the next step is to commit them. Commits are snapshots of your project at a given point in time. To commit your staged changes, run:<\/p>\n
git commit -m \"Describe your changes here\"<\/code><\/pre>\nMake sure your commit message is clear and actually describes what the new code does.<\/p>\n
Adding a Github Remote Repository and Pushing Changes<\/h3>\n
To collaborate on a project hosted on the web, such as projects on GitHub<\/a>, you first need to add a remote repository after initializing your local Git repository.<\/p>\n
The first step is to create a repository on GitHub. Go to the\u00a0Create a New Repository<\/a>\u00a0page, and create a repository.<\/p>\n
![\"Github](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/github-new-repo.webp\")
<\/p>\nOnce the repository is created, copy the repository URL and use it to add a remote repository to your local Git repository:<\/p>\n
git remote add origin <repository-url><\/code><\/pre>\nThis command sets up the connection between your local repository and the remote one.<\/p>\n
You can check if the remote repository was added successfully by running:<\/p>\n
git remote -v<\/code><\/pre>\nOnce you've added the remote repository and committed your changes, you can push them to the remote branch using
git push<\/code>:<\/p>\ngit push -u origin main<\/code><\/pre>\nThis command pushes your commits to the
main<\/code> branch of the remote repository. If you're working on a different branch, replacemain<\/code> with the correct branch name, you may need to replace it withmaster<\/code> in certain cases.<\/p>\nIf you\u2019re using Github, Git will ask for your GitHub username and password. Type in your username and enter your personal access token for the password.<\/p>\n
To create a personal token on Github, navigate to the New personal access token<\/a> page. Select the scopes that you want to control, and then click Generate Token.<\/p>\n
![\"Github](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/github-access-token-1024x642.webp\")
<\/p>\nYou\u2019ll be redirected to a page with your new token.<\/p>\n
For more information, check out Managing your personal access tokens<\/a>.<\/p>\n
After using your personal access token as a password. The
git push -u origin main<\/code> command will give you the following output:<\/p>\nEnumerating objects: 3, done.\r\nCounting objects: 100% (3\/3), done.\r\nWriting objects: 100% (3\/3), 215 bytes | 215.00 KiB\/s, done.\r\nTotal 3 (delta 0), reused 0 (delta 0), pack-reused 0\r\nTo https:\/\/github.com\/user\/repo\r\n * [new branch] main -> main\r\nbranch 'main' set up to track 'origin\/main'.<\/code><\/pre>\nYour Github repository will then host your code:<\/p>\n
![\"git](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/11\/github-repo-pushed.webp\")
<\/p>\nGit Branching<\/h3>\n
Git makes it easy to work on different features or fixes in isolation using branches. To create a new branch, run:<\/p>\n
git branch <branch-name><\/code><\/pre>\nThen, switch to that branch with:<\/p>\n
git checkout <branch-name><\/code><\/pre>\nThis allows you to work on a separate branch without affecting the main project. Once your changes are ready, you can merge the branch back into the
main<\/code> branch. For more on branches, check out this page<\/a>.<\/p>\nUndoing Changes<\/h3>\n
Mistakes happen, but don\u2019t worry! Git gives you great tools to undo errors. If you want to undo changes that haven\u2019t been committed yet, use:<\/p>\n
git checkout -- <filename><\/code><\/pre>\nThis will revert the specified file to the last committed state. If you need to undo a commit, you can use:<\/p>\n
git reset --soft HEAD^<\/code><\/pre>\nThis undoes the last commit but leaves your changes in the staging area, allowing you to re-commit them after making adjustments.<\/p>\n