I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I do have shell aliases for some things, like grabbing a PR locally (fish shell alias)
function copr
git fetch origin pull/$argv/head:pr$argv; and git co pr$argv;
end
At the end of the day, everyone has their own setups, which is normal. All that matters is that you set things up the way you like that makes you more productive.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I usually make aliases only for those that have specific parameters or are compound of more than one command.
In the other cases, I use the shell auto-completion with the TAB key.
Also, for those like this:
If you do that very frequent i think it's better a shell alias (
gs
) than a git alias (git s
)I do have shell aliases for some things, like grabbing a PR locally (fish shell alias)
At the end of the day, everyone has their own setups, which is normal. All that matters is that you set things up the way you like that makes you more productive.
I also don't mention it in the post but I have a shell alias for
git
which is justg
, so I'd dog s
gs
has an unpleasant collision withGhostScript
.