@musicmatze@social.linux.pizza
Post #2310627
2025-12-29 16:12 UTC
I feel like a lot of developers fear merge conflicts and complexity of "rebase".
That's why projects employ the rebase-merge or rebase+squash-merge workflow.
First of all: That's a unfounded fear.
Second of all: How can you expect your users to trust you w.r.t. professionalism in writing source, when you do not even show them (or have) your professionalism when using the basic tools _for_ writing source code.
Like... everyone is ranting about "AI" producing sub-par code, but then commit histories look like shit all the time with people doing "format fixed", "fixes", "more stuff" commits.
... or, in other words: LEARN TO USE THE TOOL YOU FKNAAAARGGHH MORONS!
---
Despairingly presented by someone who just tried to find out why a certain function was implemented in a certain way...
#git #github #software #sourcecode #opensource #development
Replies (1)
-
@kate@social.treehouse.systems 2025-12-31 09:50
@musicmatze@social.linux.pizza i think for hobby projects people should just do whatever they want, but any serious project should have a good git history. it makes finding bugs a lot easier when you can do a bisect without a bunch of bullshit commits. commits should always be atomic and in the correct order, so a checkout at any commit builds and passes all tests, linters and formatters