5 Git commands every developer should memorise

• Master the Git essentials first – Commands such as git clone, git status, git add, git commit and git pull handle most everyday version control tasks and are essential for every developer
• Build good version control habits – Commit small, logical changes, write clear commit messages, review your work with git status and pull the latest updates before starting new tasks
• Expand your Git skills over time – Once you're comfortable with the basics, learn commands like git push, git branch, git switch, git merge, git log and git diff to collaborate more effectively on larger projects

Git is one of the most important tools in modern software development. Whether you're building personal projects, collaborating with a team or contributing to open-source software, Git helps you track changes, manage versions and work more efficiently.

Although Git offers hundreds of commands and options, you don't need to memorise them all. A handful of essential commands can handle most day-to-day development tasks and make collaborating with others much easier.

Here are five Git commands every developer should memorise.

1. git clone

Before you can work on an existing project, you usually need to copy it from a remote repository to your computer.

The git clone command downloads the repository, including its files, commit history and branches.

Example:

git clone https://github.com/username/project.git

Why it's important:

• Creates a local copy of a repository.
• Includes the project's complete version history.
• Lets you start contributing immediately.

2. git status

This is one of the most frequently used Git commands.

git status shows the current state of your working directory, including modified files, staged changes and untracked files waiting to be added.

Example:

git status

Why it's important:

• Shows what has changed.
• Helps prevent accidental commits.
• Makes it easier to track your progress.

Many developers run this command several times while working on a project.

3. git add

Before Git can save your changes, you need to stage them.

The git add command tells Git which files should be included in your next commit.

Examples:

git add filename.js

Stage every modified file:

git add .

Why it's important:

• Prepares files for committing.
• Lets you choose exactly what to include.
• Supports cleaner, more organised commits.

4. git commit

A commit creates a snapshot of your staged changes.

Each commit should include a clear, descriptive message explaining what changed.

Example:

git commit -m "Fix login validation bug"

Why it's important:

• Saves your work in the repository.
• Creates a meaningful project history.
• Makes collaboration easier for other developers.

Write commit messages that describe why the change was made, not just what changed.

5. git pull

Projects often change while you're working.

The git pull command downloads the latest updates from the remote repository and merges them into your local branch.

Example:

git pull origin main

Why it's important:

• Keeps your local project up to date.
• Reduces merge conflicts.
• Helps you stay synchronised with your team.

It's a good habit to pull the latest changes before starting work each day.

Bonus Git commands worth learning

Once you're comfortable with the basics, consider learning these additional commands:

• git push – Upload your committed changes to the remote repository.
• git branch – View, create or delete branches.
• git checkout or git switch – Move between branches.
• git merge – Combine changes from different branches.
• git log – View the project's commit history.
• git diff – Compare changes between files or commits.

These commands become increasingly useful as you work on larger projects.

Tips for using Git effectively

To build good Git habits:

• Commit small, logical changes instead of one large commit.
• Write clear and meaningful commit messages.
• Pull the latest changes before starting new work.
• Create branches for new features or bug fixes.
• Review your changes with git status before committing.
• Back up your work by pushing changes regularly.

Good version control practices make development smoother and reduce the risk of losing important work.

Nigeria’s AI potential underestimated due to infrastructure gaps

Previously, TheRadar reported that a Nigerian entrepreneur and technology expert, Elizabeth Jack-Rich, said artificial intelligence (AI) remained undervalued across Nigeria and the wider African continent due to a narrow understanding of what truly drives the technology.

Speaking at an AI-focused event in Washington, D.C., Jack-Rich argued that discussions around AI had been centred on software innovation, while ignoring the fundamental role of physical infrastructure and resource supply.