The linked article Show archive.org snapshot found a simple way to rewrite legacy git aliases to make them work with differently named default branches

• Step 1: Decide which is the most common default branch name of your projects, e.g. master. Define it as the global init.defaultBranch git configuration :

git config --global init.defaultBranch master

• Step 2: Overwrite the value in each project directory that uses different defaults

# cd /path/to/project, then run:
git config --local init.defaultBranch main

• Step 3: Adjust your ~/.gitconfig aliases to use the defaultBranch variable, e.g.:

[alias]
  merge_request = push origin HEAD -o merge_request.create -o merge_request.target=master -o merge_request.draft

Growing Rails Applications in Practice

Check out our e-book. Learn to structure large Ruby on Rails codebases with the tools you already know and love.

• Introduce design conventions for controllers and user-facing models
• Create a system for growth
• Build applications to last

Read more Show archive.org snapshot

becomes

[alias]
  merge_request = !git push origin HEAD -o merge_request.create -o merge_request.target="$(git config init.defaultBranch)" -o merge_request.draft

• Step 3: Adjust your ~/.bashrc aliases to use the defaultBranch variable

alias gdm='git diff --color-moved=dimmed_zebra master'

becomes

alias gdm="git diff --color-moved=dimmed_zebra $(git config init.defaultBranch)"

Caveat

Aliases are evaluated only once whenever you open a new terminal. This means that you cannot expect these aliases to adjust when you cd from one project into another. You need to open a new shell in this case (or source the ~/.bashrc).