Git is my buddy: Effective Git as a solo developer

Re:Git is my buddy: Effective Git as a solo developer by w0mbat on Tuesday February 23, 2021 @01:09PM (#26240544)

Absolutely. This guy has too many rules.

When I work alone I'm climbing a mountain, and Git is the rope. I can fall, but I won't fall far. I commit as often as I want to. The log is not a story for someone else to read later, it's the way I get to the top.

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by jeremyjh on Tuesday February 23, 2021 @03:20PM (#26242367)

I find commit logs useful even if I'm the only person ever reading them. I like to be able to git blame on a line and be reminded of the context in which I did something and what I was trying to solve. I don't bother to pretty up my feature branches though, I just squash them so that master has a clear story

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by SilverRed on Tuesday February 23, 2021 @05:09PM (#26243571)

How we do it at work is every single commit message must have a ticket number in it. This is super easy to do and super useful. Even if the commit message is "fix exception #1823" you can go and look up #1823 and see what that issue was to make sure you don't reintroduce it with your change. You will always find more info and context in the ticket than in git commit messages.

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by w0mbat on Wednesday February 24, 2021 @05:49PM (#26257244)

I hate this. Often I am rewriting a bad comment, or improving the working code I checked in yesterday whose ticket has already been closed. Deleting an unneeded #include. All kinds of stuff for which there is no open ticket.

This kind of rule prevents people from maintaining the code base as they go. I have literally quit a company because of bullshit such as this. I was a senior engineer and could not fix a typo in a comment without a bug number and two code reviews.

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by SilverRed on Wednesday February 24, 2021 @09:28PM (#26258997)

This has been a non issue for me. I just slap minor fixes in with other tickets even if they are not related. Usually I just drop a comment in the review page with "saw this other issue and fixed it"

Short circuiting the review and QA steps is not ideal. A reviewer should see the change is just a comment typo fix and accept it even if it has nothing to do with the current ticket.

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by w0mbat on Wednesday February 24, 2021 @05:52PM (#26257270)

The log is a useful byproduct, but it's not the product.

[ Parent | on HN ]

Re:Git is my buddy: Effective Git as a solo developer by mplanchard on Tuesday February 23, 2021 @01:32PM (#26240881)

This is an excellent metaphor, thank you. I’m going to add it to the bag of metaphors I use when explaining git

[ Parent | on HN ]