How do you use git when developing alone?

Question

git

I work as a freelancer, the projects are small and I lead all of them alone, without a team.
Tried to use the Git Flow technique to get the job done. At first, everything is fine, branches for features are created, small commits with a meaningful description, merges. But in the end, in the process of creating, all this gets boring and rolls down to commits immediately in master from a dozen files with several features and a description like "big update".
How do you deal with it? And in general, is Git Flow needed here, or should I give up on everything and work as it works?

Answer 1

For myself, one git, it seems to me, is needed only as a "time machine" and a "reverse roadmap".
That is, to be able to look at an earlier version of the code and to find in the commit stream when there were any specific changes.
By and large, nothing but commits to the master is required here. Unless small commits with meaningful writing of changes are desirable, and not pieces of what you yourself will not remember in a week.

Answer 2

Just committing any meaningful changes with a sane little comment

Answer 3

I try to use git, without gitflow, sometimes it saves my own ass when I nagovnokodil and need to restore the previous version.

Answer 4

I use the dev branch for development. And by the end of each day I make commits to the master branch.

Answer 5

I found one funny picture on the topic of the ability to correctly name commits) At one time it made me very happy)

Answer 6

I use svn purely as a remote repository, so that from anywhere you can take the code and start adding it.
versioning is not needed at all when you work alone. there was never even a need to look into history.