That's reasonable. I have aliases for a lot of my more frequent tasks like this. It's irrational in this case so maybe I should just get over this — but I feel a little nervous about making aliases for anything I use infrequently in case I forget what the underlying execution is.
Full-time web dev; JS lover since 2002; CSS fanatic. #CSSIsAwesome
I try to stay up with new web platform features. Web feature you don't understand? Tell me! I'll write an article!
He/him
I second using an alias. If you forget the alias you set, you can do git config -l to list all config values, including aliases, and just scan through them.
Or, if you remember the alias name, you can do get config --get alias.alias-name to show what it's an alias of.
That's reasonable. I have aliases for a lot of my more frequent tasks like this. It's irrational in this case so maybe I should just get over this — but I feel a little nervous about making aliases for anything I use infrequently in case I forget what the underlying execution is.
...because you currently remember it so well that you wrote a post for your own future reference? 😛
I second using an alias. If you forget the alias you set, you can do
git config -lto list all config values, including aliases, and just scan through them.Or, if you remember the alias name, you can do
get config --get alias.alias-nameto show what it's an alias of.thanks , I didn't know that... It's useful for more complicated aliases.