Great article, and while reading through I was thinking "maybe I don't want to encourage each developer to use git differently, maybe I want a set standard across the business, so that when things go wrong, everyone knows what should have happened, and can get back to it quickly" - and as a result - "I get your point, but maybe aliases are better than changing default behaviour."
And then you answered that too! :)
Enjoy the power of typing less with aliases or a push configuration that better matches your workflow!
On that point though, I have to point out that your chosen aliases are remarkably long, while being shorter than the original commands. Though yes, I understand it's for the benefit of the article. My git puf is akin to you git pushup - but maybe I'm over zealous, and I recognise that the price I pay for using shorter aliases is that my brain jumps through more hoops when I'm teaching someone else / using someone else's machine.
I think an alias like puf is fine because I use it regularly. I really only use longer ones if it's something I don't use often and the longer form is easier to remember.
As long as the alias is shorter than the alternative command then generally I don't overthink it.
Definitely love your point about making standards across the business. We enforce pretty strict coding and commit standards but are generally pretty flexible about the git tools (CLI or GUI) and preferences to the developer as we hope our linters and CI policies stop anything untoward.
Definitely keen to look at applying some standards to git configs and practice though :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article, and while reading through I was thinking "maybe I don't want to encourage each developer to use git differently, maybe I want a set standard across the business, so that when things go wrong, everyone knows what should have happened, and can get back to it quickly" - and as a result - "I get your point, but maybe aliases are better than changing default behaviour."
And then you answered that too! :)
On that point though, I have to point out that your chosen aliases are remarkably long, while being shorter than the original commands. Though yes, I understand it's for the benefit of the article. My
git pufis akin to yougit pushup- but maybe I'm over zealous, and I recognise that the price I pay for using shorter aliases is that my brain jumps through more hoops when I'm teaching someone else / using someone else's machine.I think an alias like
pufis fine because I use it regularly. I really only use longer ones if it's something I don't use often and the longer form is easier to remember.As long as the alias is shorter than the alternative command then generally I don't overthink it.
Definitely love your point about making standards across the business. We enforce pretty strict coding and commit standards but are generally pretty flexible about the git tools (CLI or GUI) and preferences to the developer as we hope our linters and CI policies stop anything untoward.
Definitely keen to look at applying some standards to git configs and practice though :)