Post #1812380
2026-04-30 07:31 UTC
Sometimes you really don’t want to look over the commit history of your colleagues. As long as it’s a small feature, a single commit is a pretty good option.
Rather than:
implemented X
forgot this
oh, this was not needed
now tests actually pass
oops
fixed this
should be ready
Replies (2)
-
@elvith@feddit.org 2026-04-30 08:05
That’s basically my commit history for every repo where I need the pipeline to run to see if everything works.
-
@expr@piefed.social 2026-04-30 12:37
It’s fine if the changes belong in a single commit. Otherwise, an interactive rebase to craft a clean, quality history before merging is much, much better.