undefined | Better HN

0 pointstrashb2mo ago0 comments

  gitcli != git

If you want to create (or use) another git client that makes removing a secret easy for you and your team you are free to do so.

> It was never about whether it was possible. It was about how it's being done.

That's what I was saying originally, no need to change the infrastructure but you can change how you interact with it.

> Arguing that there shouldn't be a simpler way to remove an enormous security flaw feels a bit disingenuous.

First of all, skill issue educate your employees. Secondly, this is a well considered and a huge part of why git is preferred over older systems like SVN or SCCS especially in an open source context where you are distributing your code through unknown channels and where the publisher might have moved on.

Perhaps Git is not the best VCS for your situation. But I think that if you try other options you will run into bigger problems, there is a reason git became the standard in the industry.

[0] https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3... [1] https://git-scm.com/book/en/v2/Getting-Started-The-Command-L...

0 comments

1 comments · 1 top-level

mexicocitinluez2mo ago

> First of all, skill issue educate your employees. Secondly, this is a well considered and a huge part of why git is preferred over older systems like SVN or SCCS especially in an open source context where you are distributing your code through unknown channels and where the publisher might have moved on.

If you're entire argument rests on people being perfect, it's a trash argument.

Implying that accidents don't happen when you have skills is absurd.

j / k navigate · click thread line to collapse