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

PowerShell: Get Actual Error

I was having hard time to find the reason why I was not able to find a custom method in a .Net DLL. Find your Assembly: PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts > [appdomain]::currentdomain . getassemblies() | Where - Object FullName - Match "MyAssembly" GAC Version Location --- ------- -------- False v4 . 0.30319 C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts\Tools\MyAssembly . dll PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts & gt; $ a = [appdomain]::currentdomain . getassemblies() | Where - Object FullName - Match "MyAssembly" PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts & gt; $ a GAC Version Location --- ------- -------- False v4 . 0.30319 C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts\Tools\MyAssembly . dll When I was trying to get the Types in the assembly, I was getting the exception: PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts > ...
Post a Comment
Read more

Enable Trace on Dynamcis 365 on premise using PowerShell

Enable trace settings through Windows PowerShell Note These changes made in Windows PowerShell do not update the Registry. These changes update the DeploymentProperties and ServerSettingsProperties tables in the MSCRM_CONFIG database. Register the cmdlets 1.      Log in to the administrator account on your Microsoft Dynamics CRM server. 2.      In a Windows PowerShell window, type the following command: Add-PSSnapin Microsoft.Crm.PowerShell To obtain a list of the current settings, type the following command: Get-CrmSetting TraceSettings Set the trace settings 1.      Type the following command: $setting = Get-CrmSetting TraceSettings 2.      Type the following command to enable tracing: $setting.Enabled=$True 3.      Type the following command to set the trace settings: Set-CrmSetting $setting 4.      Type the following command...
Post a Comment
Read more

Notepad++ Error for 64bit - ShellExecute failed (2): Is this command correct?

Cause : It happens when you set Notepad++ to "run as" administrator on Windows 7. Fix:  To fix this, you need to manually edit the registry of your system to create a new option in pop-up menu to open files with Notepad++ Step 1 : Delete existing  Edit with Notepad++  entry from registry Go into your registry as an administrator (Run -> regedit) and search for notepad++.exe. Find the key under  HKEY_CLASSES_ROOT  that has an entry with the  Edit with Notepad++  (or maybe  Edit with &Notepad++ ) and delete the entire key. Right click and you should see that you no longer have that option. Step 2 : Create new entry Open with Notepad++ Go to: HKEY_CLASSES_ROOT\*\shell Create a new key under shell called  OpenWithNotepad  and create a subkey under that called  command . In the  OpenWithNotepad  key the default string is what you want the context menu item to be called. I set it to  Open with Not...
Post a Comment
Read more