For those who don't know, you can make git pish have the same effect as git push by creating an alias between pish and push. Useful to do for any misspellings you make more than once.

$ git config --global alias.pish push

Cannot for the life of me tell if this is a serious suggestion.

I've actually done this for a couple commands I screw up often enough -- I have this in my bashrc:

  alias dumbtypo="echo 'LEARN TO TYPE, MORON'"
  alias sl="dumbtypo; ls"
  alias rbuy="dumbtypo; ruby"
  alias pytohn="dumbtypo; python"
  alias brwe="dumbtypo; brew"
  alias arhcey="dumbtypo; archey"

I'm incredulous that 'pythong' is not in there.

I can't not-type it.

You ... type "python"? Not pyt[tab]?

I type pythong all the time, too.

I was worried I was the only one!

if you sudo apt install sl you will have more fun making that typo ;)

there are a couple things I typo frequently enough I've seriously considered it...

It is-- what is the perceived downside?

You have a giant list of common typos, making you a worse and worse typer as years go on, until you are mashing your head on the keyboard to type anything.

I dunno, I don't think that would really happen. I'm always trying to type the same word (I don't say "pish" in my head, after all, I think "push"), so it doesn't seem to be a random walk away from correctness, just some wavering around it. And it's not like I have that many commands I need to type commonly enough to make an alias for-- maybe a couple dozen? And for most of them, I don't make typos so I don't feel the need to make an alias.

alias gp="git push" has probably saved me hours of my life

Amen.

My bashrc has so many of these, and they're probably among the most common commands I use daily!:

    alias gs="git status"
    alias gb="git branch"
    alias grh="git reset --hard"
    alias gcdf="git clean -df"
    alias gf="git fetch"
    alias gp="git pull"
    alias gdom="git diff origin/master"
    alias gdomn="git diff --name-status origin/master"
    alias gd="git diff"
    alias gl="git log"
    alias glm="git log --author <my_name>"
    alias gc="git checkout"
    alias gcm="git checkout master"

I agree, but I am just too lazy for that. Mine are all one char:

  alias b='/usr/local/bin/git checkout -b'
  alias a='/usr/local/bin/git add
  alias d='/usr/local/bin/git diff HEAD'
  alias c='git commit -m'
  alias i='/usr/local/bin/git pull origin'
  alias o='/usr/local/bin/git branch -avv | grep "\*" | cut -d\ -f 2 | xargs -n 1 /usr/local/bin/git push -u origin'

plus:

  alias g='/usr/local/bin/git log --graph --oneline --decorate 
  alias v='/usr/local/bin/git branch -avv'--all'
  alias h='/usr/local/bin/git log -p'

can be useful.

Am I a bad person for creating SVN-style aliases for git?

From my .gitconfig:

    [alias]
            st = status
            ci = "!git add -u && git commit"
            di = diff

I come from an SVN background, I've since switched to Mercurial for my personal projects, and intensely dislike git, but have to use git at work, so I finally said "enough is enough" and made aliases so I can use git like svn/hg.

I use gcm for `git commit -m `, interestingly.

I only use a few git aliases, most things I'd rather type out.

I use Git Goodies, great list of aliases - https://github.com/qw3rtman/gg

Aliasing gs may be a bad idea, there is actually a command named like that (it's part of GhostScript)

Of course to each his own, but honestly, nothing I work on involves Ghostscript (or Postscript tbh) so not too much of a concern to me.

It's just so much quicker to recall stuff: [g]it [s]tatus :)

I have a similar set, plus

alias goto='git checkout'

Or how about git commit with a dummy message? :)

Oh dear. That reminds me of a story I saw here on HN at some point (might have been in the comments) about a dev team that didn't insist on any commit messages in their VCS, so everyone just put in a '.' to meet the requirement that a commit had to have a message for whatever source control system they were using.

My team doesn't have a strict commit message style guide, but good god it better be at least mildly descriptive of what's in the commit.

(I know you're joking, the thought of a 3 character alias to commit with a dummy message just sent shivers down my spine :)

Like this?

  $ cat << EOF > ~/.commit_reasons; strfile ~/.commit_reasons
  Testing...
  %
  Testify...
  %
  Testarossa...
  %
  Does it work yet?
  %
  How bout now?
  %
  Oops.
  %
  Fixed a thing.
  %
  EOF
  
  $ fortune ~/.commit_reasons | cowsay | git -F -

Even better: https://news.ycombinator.com/item?id=5666160

looks like oh-my-zsh ships with this... couldn't figure out why I had it already.

Git even has a wonderful autocorrect feature that you can enable with "git config --global help.autocorrect 1" This fixes commands like git pish or git ermote

For me it tends to be

$ git poop

as opposed to `git log`?

In case that wasn't a joke - no, `git pop`.

i constantly do:

git pull upsteam dev

For me it usually is "git remove" instead of "git remote".