News for hackers. Stuff that matters.
Re:Autosaved: A Go utility for autosaving progress in Git pr... by gouggoug on Wednesday January 12, 2022 @05:47PM (#29913831)
I have nothing against this tool in particular;

I am however quite worried that this kind of tool will just enable this already terrible habit that a lot of developers have; which is to mindlessly commit changes and then make PRs full of "asdf", "typo", "fixing comma", "blaaaaa".

With this tool, these developers won't even have to waste time typing `git commit` and will happily submit PRs as a bunch of "autosaved" commits.

This further reduces git to being just a means to an end: the end being able to just mindlessly push code over a fence and see it magically deployed.

Re:Autosaved: A Go utility for autosaving progress in Git pr... by kazinator on Wednesday January 12, 2022 @06:05PM (#29914024)
It doesn't, because these backups go to a parallel branch.

What it's doing though is polluting your git repo with these commits.

A daemon which backs up projects that you're working on, so you have fine-grained snapshots to go back to if you screw up is a good idea.

Backing up only files known to git, and backing them up into git, is not such a hot idea.

Re:Autosaved: A Go utility for autosaving progress in Git pr... by herval on Wednesday January 12, 2022 @06:40PM (#29914435)
> This further reduces git to being just a means to an end: the end being able to just mindlessly push code over a fence and see it magically deployed.

I fail to see how that would be a bad thing?

Re:Autosaved: A Go utility for autosaving progress in Git pr... by gouggoug on Wednesday January 12, 2022 @06:44PM (#29914487)
git's purpose is to track change and provide meaningful insights into code written by many different people.

The fact that you can use it to deploy is just a side effect and using git solely because it makes it easier to deploy changes is thoroughly missing the point.

Re:Autosaved: A Go utility for autosaving progress in Git pr... by ferdowsi on Wednesday January 12, 2022 @08:45PM (#29915780)
Every large organization I've been in performs a squash merge with the PR description as merge commit summary, because intermediary commits are always noise like "fix tests" and "didn't actually fix, do it now". That's a story not worth reading.