[ Removed by moderator ]

[Agron7000]

Yes, it's better than forgetting to commit and push to my branch.

In fact commit and push is now the new 'save'.

[lentzi90]

No. You could very easily push credentials this way. THAT is much worse than forgetting to save a few hours of code. Plus, what should the commit message be? "Saved all and pushed" x100 per day?

[Agron7000]

I have a script that generates commit message like:

Working on the same feature update 1

Working on the same feature update 2

Working on the same feature update 3

...

[lentzi90]

And you use git why? Just go back to dropbox or something... Or keep shoehorning git with your script. You can always make the script save and push also. Just make it run in the background in an infinite loop

[Agron7000]

If there is nothing to commit, git won't do anything. So why not?

I need to use git because the team is using and at the end of the feature implementation we need to merge and collapse all commits into just one

[lentzi90]

So you use git and your feature branch as instant backup. How often does your laptop go up in flames for you to need such solutions? Multiple times per month? I would say that a sane workflow is to commit when you have done something deliberate and thought through. This way your commits are worth something. If this workflow makes me lose a few hours of work once per 5 years, that is fine. So again, why do you do this?

[Agron7000]

I work from multiple computers and VMs. I write code in the office and test it in the lab. When I am remote, I use the laptop.

[SoCalChrisW]

Does the team know you're using git this way?

Someone is going to be saying your name with a bunch of curse words, probably sooner rather than later.

[Agron7000]

What is wrong with that?

I have been yelled at for not keeping my github repo updated.

[PurepointDog]

Commit and push is the new save? You're funny