Ask HN: Can we do better than Git for version control?

Re:Ask HN: Can we do better than Git for version control? by retpoline__ on Sunday December 10, 2023 @04:41AM (#38590396)

This is funny because in PR oriented development I started treating commits in the same way as "save" in IDE,

it's just backup of current state with irrelevant commit message. Everything is described at the end of the work in PR's description and squash merged.

[ Parent | on HN ]

Re:Ask HN: Can we do better than Git for version control? by from-nibly on Sunday December 10, 2023 @08:58AM (#38591537)

But then you can't use blame to look at the current code state. And it also becomes a nightmare to revert your changes.

[ Parent | on HN ]

Re:Ask HN: Can we do better than Git for version control? by dolni on Sunday December 10, 2023 @10:50AM (#38592328)

Giant PRs that are squashed into one commit are an anti-pattern. Every commit should contain exactly one logical change AND a descriptive commit message.

Unfortunately a good chunk of the industry doesn't have the discipline to do this.

If you have ever worked in a project where there was discipline around committing, you know there is lots of value in doing so (rebasing becomes easier, you unlock the power of bisect, log is actually useful).

[ Parent | on HN ]

Re:Ask HN: Can we do better than Git for version control? by argulane on Monday December 11, 2023 @05:53PM (#38606616)

This!

Also doing PR code review is soo much nicer if each commit is logically self contained with a nice commit message.

[ Parent | on HN ]