Idiot Proof Git

Re:Idiot Proof Git by cnity on Wednesday November 09, 2022 @12:08PM (#33534597)

If the employer I worked for started micro-managing the way I use my tools (that affects nobody else) I would consider leaving, honestly. If I rebase on a branch that hadn't been shared with someone else, why does it matter what my boss or team thinks about that approach?

Code styles are one thing, what I type into my terminal is another.

[ Parent | on HN ]

Re:Idiot Proof Git by gardenhedge on Wednesday November 09, 2022 @04:30PM (#33538161)

When you commit you're sharing with your team and future team. I think it's fair to have a set of agreed guidelines around that. What if you wanted to put all your commit messages as "cnity did it"?

[ Parent | on HN ]

Re:Idiot Proof Git by bacon_waffle on Wednesday November 09, 2022 @09:47PM (#33541564)

I agree with the post you're responding to, and make a lot more commits than I share with my team. Pushing commits to a shared branch is where work is shared.

At my current employer, we used to use Perforce, and in that world you're totally right that committing (submitting in Perforce terminology, IIRC) did share changes. In that context, we developed a lot of bad patterns, losing code or holding up other people's work while a developer got their work ready to share. Transitioning to git has been super painful, due mainly to people treating git as if it's the same sort of thing as Perforce...

[ Parent | on HN ]

Re:Idiot Proof Git by cnity on Thursday November 10, 2022 @04:29AM (#33544132)

It's simple: I wouldn't do that. Do we need guidelines to not delete repositories too?

[ Parent | on HN ]

Re:Idiot Proof Git by gardenhedge on Friday November 11, 2022 @03:05PM (#33566093)

Yes of course

[ Parent | on HN ]