You are viewing a single thread.
View all comments View context
2 points

I try to structure my commits in a way that minimizes their blast radius, which usually likes trying to reduce the number of files In touch per commit.

For example, my commit history would look like this:

  • Add new method to service class
  • Use new service class method in worker

And then as I continue working, all changes will be git commit --fixuped to one of those two commit’s hashes depending on where they occur.

And when it’s time to rebase in full, I can do a git rebase master --interactive --autosquash.

permalink
report
parent
reply
1 point

This is the way! Small commits with descriptive commit names, then just fixup into a few feature commits. Makes rebase a breeze.

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 3.4K

    Monthly active users

  • 1K

    Posts

  • 38K

    Comments