Re: Let us not call it git blame
- From
- demerphq <demerphq@gmail.com>
- Date
- Mar 3, 2023, 08:28 UTC
- Message-ID
- <CANgJU+XT3h4b40Nr8uq_j4NyY0ka43vPghN4fJx8B=qcCHoUaA@mail.gmail.com>
- In-Reply-To
- <SY6P282MB378273980F5BC9084EEF74EF92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
On Thu, 2 Mar 2023 at 23:21, Dinesh Dharmawardena <dinesh_dh@outlook.com> wrote:
> > Hi > > I am writing to you to request that the term blame in git blame be replaced with something that does not sound so blameful. I’m an SRE and we actively try promote a blameless culture as such industry tooling should also follow suit imo. Progressively phasing this term out with a better alias would be great.
Just set up an alias that maps `git credit` to `git blame`, and you are done.
$ git config --global alias.credit blame
I dont think there is or ever will be much traction to rename this command, it is short and self descriptive.
Blameless culture is great, but it is about "not finger pointing", not about what tools you use. Your company's management and internal culture keepers are more important for setting this tone than the tools you use. If they don't actually practice not finger pointing then renaming the tool won't dont anything, and if they do actually practice then the name of the tool won't matter either.
cheers, Yves
-- perl -Mre=debug -e "/just|another|perl|hacker/"