How to See All Branches in Git?

Branches are a core feature in Git, allowing developers to work on separate features or bug fixes without affecting the main project code. Viewing all branches within a repository—both locally and remotely—is essential for understanding the project’s current state and managing workflows effectively.

In this post, we’ll explore the different ways to see all branches in Git, explain the differences between local and remote branches, and share best practices for branch management.

Why View All Branches in Git?

Knowing how to list all branches in a Git repository helps with:

1. Managing Development Workflows: You can keep track of various branches created for features, bug fixes, or releases.
2. Collaborating with Teams: Checking branches enables teams to stay up-to-date with each other’s work, avoiding conflicts and redundancy.
3. Reviewing Repository Structure: Understanding which branches are active and their purposes contributes to an organized and maintainable project.

---

Prerequisites

To follow along with this guide, make sure you:

• Have Git installed on your computer.
• Have a repository with branches cloned or created locally.
• Are familiar with Git commands and basic version control concepts.

---

Types of Branches in Git

Before we dive into the commands, it’s essential to understand the two main types of branches:

1. Local Branches: Branches that exist only on your local machine.
2. Remote Branches: Branches that exist on the remote server (e.g., GitHub, GitLab) and are typically shared with team members.

Let’s look at how to view both types of branches.

---

How to See All Local Branches in Git

If you want to see only the branches on your local machine, use the following command:

git branch

This command will list all branches currently in your local repository, with the active branch (the one you’re currently on) highlighted with an asterisk (*).

Example Output:

* main
  feature/new-feature
  bugfix/fix-typo
  release/v1.0

In this example, you can see three branches besides the active branch, main. Each of these branches is a local branch.

---

How to See All Remote Branches in Git

To view all branches on the remote repository (e.g., on GitHub or GitLab), use:

git branch -r

This command displays only the remote branches, prefixed with the remote name (typically origin unless you’ve renamed it).

Example Output:

origin/main
origin/feature/new-feature
origin/bugfix/fix-typo
origin/release/v1.0

Here, origin indicates the default remote for these branches, and the branch names mirror those on the remote repository.

Tip: If you don’t see the expected branches, you may need to fetch updates from the remote repository using git fetch.

---

How to See All Branches (Local and Remote)

To view both local and remote branches in a single list, you can use:

git branch -a

The -a flag lists all branches, providing a comprehensive view of every branch available in your repository.

Example Output:

* main
  feature/new-feature
  bugfix/fix-typo
  release/v1.0
  remotes/origin/main
  remotes/origin/feature/new-feature
  remotes/origin/bugfix/fix-typo
  remotes/origin/release/v1.0

In this output:

• Branches without the remotes/origin/ prefix are your local branches.
• Branches prefixed with remotes/origin/ are remote branches.

---

Additional Git Branch Listing Options

To filter and format your branch listing further, Git offers some additional options:

1. Listing Branches by Last Commit Date: If you want to see branches sorted by the date of the last commit, use:

   git branch --sort=-committerdate

This command helps you identify recently active branches, which can be useful for cleaning up old branches or prioritizing active work.

2. Displaying More Information with --verbose: The -v or --verbose option shows the latest commit on each branch:

   git branch -v

#### Example Output:

   * main                 b97f6c3 Initial commit
     feature/new-feature  4a1b3f5 Add new feature
     bugfix/fix-typo      e9c7b2a Fix typo in readme

3. Filtering by Branch Names: You can use patterns to filter branch names. For example, to list only branches that contain the word “feature”:

   git branch --list "*feature*"

This helps locate branches with specific naming conventions, such as feature/* branches.

---

How to Fetch Remote Branches Without Merging

If you’ve noticed that remote branches seem outdated or missing, you might need to fetch updates without merging them into your local branches:

git fetch --all

Fetching brings the latest branch references from the remote server without changing any of your local branches.

---

Deleting Branches: Cleaning Up Your Branch List

Over time, repositories can become cluttered with branches that are no longer in use. Here’s how to clean up:

1. Delete a Local Branch:

   git branch -d branch-name

Replace branch-name with the branch you want to delete. Use -D instead of -d to force delete if the branch hasn’t been merged.

2. Delete a Remote Branch:

   git push origin --delete branch-name

This command removes the branch from the remote repository, making it unavailable to other collaborators.

Note: Deleting branches should be done with caution, especially when working on shared repositories. Always communicate with team members before deleting shared branches.

---

Practical Example: Listing Branches in a Workflow

Let’s walk through a quick example of using these commands in a typical workflow:

1. Check Local Branches:

   git branch

You’ll see a list of your local branches. Let’s assume you notice an outdated branch.

2. View Remote Branches:

   git branch -r

Verify if the outdated branch exists on the remote as well.

3. Fetch Updates:

   git fetch --all

Ensure you have the latest references from the remote repository.

4. Delete the Outdated Branch:

   git branch -d outdated-branch

If it’s also on the remote:

   git push origin --delete outdated-branch

This approach keeps your branch list clean and organized, helping you focus on active development.

---

Best Practices for Branch Management

1. Use Descriptive Branch Names: Clear, descriptive names make branch management easier, especially in larger teams.
2. Regularly Delete Outdated Branches: Clean up branches you no longer need to keep your repository organized.
3. Use Patterns for Quick Filtering: Adopt naming conventions, such as feature/*, bugfix/*, and release/*, which help locate branches easily.
4. Communicate with Team Members: Before deleting shared branches, always inform team members to avoid conflicts or lost work.

---

Conclusion

Being able to see all branches in Git is fundamental for managing code, tracking development work, and collaborating effectively. Whether viewing local, remote, or all branches, the commands in this guide provide flexibility for handling branch management tasks. By following these steps and best practices, you can maintain an organized repository, making it easier for you and your team to focus on building great software.