Skip to main content

10 Git Aliases for a Faster and More Productive Workflow

Using Git as your go-to code versioning tool is a daily routine for developers, often managed through the command line. Even if you prefer a dark-themed GUI, sometimes you just need to dive into the CLI.

In this article, we'll explore 10 Git aliases that can streamline your workflow, whether you're working solo or within a team. Let's dive in and make your Git game stronger!

Setting Git Aliases

Your Git aliases are usually stored in your user configuration file, typically located at ~/.gitconfig. You can manually set aliases using commands like git config alias.s 'status -s'.

Listing Git Aliases

To see all your Git aliases, use the command git config --list --show-origin, which lists all Git configurations along with their origins.

1. Git Status

Do you find yourself frequently checking your Git status? Create an alias for it:

bas
[alias]
    s = status

Now you can simply type git s to check your status.

2. Git Checkout

Switching between branches is a common task. Make it easier with an alias:

bash
[alias]
    co = checkout

Try it out with git co feat/add-popup.

3. Create a New Branch

Creating new branches? Save some keystrokes:

bash
[alias]
    cob = checkout -b

Use it like git cob feat/add-popup.

4. Delete a Branch

Need to remove a branch? Use this alias:

bash
[alias]
    del = branch -D

Delete branches with git del feat/add-popup.

5. List All Branches

Having trouble keeping track of branches? Use this alias to list them:

bash
[alias]
    br = branch --format='%(HEAD) %(color:yellow)%(refname:short)%(color:reset) - %(contents:subject) %(color:green)(%(committerdate:relative)) [%(authorname)]' --sort=-committerdate

Try it with git br.

6. Git Commit

Commit often? Create a quick alias:

bash
[alias]
    save = !git add -A && git commit -m 'chore: commit save point'

Simply type git save to commit your changes.

7. Rollback Changes

Need to undo your last commit? Use this alias:

bash
[alias]
    undo = reset HEAD~1 --mixed

Rollback with git undo.

8. Clean All Changes

Want to start fresh? Clean up your changes with:

bash
[alias]
    res = !git reset --hard

Clean up with git res.

9. Push Changes to Upstream

Ready to push your changes? Use this shortcut:

bash
[alias]
    done = !git push origin HEAD

Push with git done.

10. Git Log

Lastly, a useful alias for viewing logs:

bash
[alias]
    lg = !git log --pretty=format:\"%C(magenta)%h%Creset -%C(red)%d%Creset %s %C(dim green)(%cr) [%an]\" --abbrev-commit -30

View logs with git lg.

In Summary

These 10 Git aliases will supercharge your productivity and streamline your workflow, whether you're a solo developer or part of a team. Add them to your ~/.gitconfig file and watch your Git game soar!

Comments

Post a Comment

Popular posts from this blog

What is release, and what is a deployment?

T o understand the concepts and the technical implementation in many tools, you need to know how tool vendors define the difference between a release and a deployment. A  release  is a package or container containing a versioned set of artifacts specified in a release pipeline in your CI/CD process. It also includes a snapshot of all the information required to carry out all the tasks and activities in a release pipeline, such as: The stages or environments. The tasks for each one. The values of task parameters and variables. The release policies such as triggers, approvers, and release queuing options. On the other hand,  Deployment  is the action of running the tasks for one stage, which results in a tested and deployed application and other activities specified for that stage. Starting a release starts each deployment based on the settings and policies defined in the original release pipeline. There can be multiple deployments of each release, even for one stage. ...
Post a Comment
Read more

Delivery cadence and three types of triggers

Both the release and stages make use of triggers. There are three types of triggers we recognize. Continuous deployment trigger You can set up this trigger on your release pipeline. Once you do that, your release pipeline will trigger every time a build completes, and a new release will be created. Scheduled triggers This speaks for itself, but it allows you to set up a time-based manner to start a new release—for example, every night at 3:00 AM or 12:00 PM. You can have one or multiple schedules per day, but it will always run at this specific time. Manual trigger With a manual trigger, a person or system triggers the release based on a specific event. When it's a person, it probably uses some UI to start a new release. When it's an automated process, some events will likely occur. You can trigger the release from another system using the automation engine   Navigation Traditional IT deployment cycle What is Continuous Delivery? What is release, and what is a deployment? Azure...
Post a Comment
Read more

Considerations for deployment to stages

When you have a clear view of the different stages you'll deploy, you need to think about when you want to deploy to these stages.  Continuous Delivery is about deploying multiple times a day and can deploy on-demand. When we define our cadence, questions that we should ask ourselves are: Do we want to deploy our application? Do we want to deploy multiple times a day? Can we deploy to a stage? Is it used? A typical scenario we often see is continuous deployment during the development stage. Every new change ends up there once it's completed and builds. Deploying to the next phase doesn't always occur multiple times but only at night. When designing your release strategy, choose your triggers carefully and consider the required release cadence. Some things we need to take into consideration are: What is your target environment? Does one team use it, or do multiple teams use it? If a single team uses it, you can deploy it frequently. Otherwise, it would be best if you were a ...
Post a Comment
Read more