I’m sure you could write a script that would do this for you, or a plugin for your editor of choice. Why would you want to, though?
My usual workflow since I’ve started using git (which, mind you, was only last week) is to make a logical group of changes, then pause for a moment to add changed files, commit with a concise but clear message of what I’ve changed, then push to a remote branch. E.g.:
$ git add .
$ git commit -m “Added social media icons to global header.”
$ git push origin develop
If you automatically commit and push changes on filesave, you lose this coherency granted by commit messages, which to me is a huge part of why git makes sense for my workflow.
The way we do it at work is that any database changes get’s applied manually. So, if you’re needing to change the Users table, you write the SQL for it locally, update the database using the tested SQL and then push the changes.
@chrisburton Git is very complex, but you don’t need to learn all of it for basic use. There are also a few GUI’s, github makes one, that simplifies it a bit more. I use git all the time and I only know enough to keep me working, but sometimes not out of trouble :P
@traq, no, I completely understand where you’re coming from… what I was getting at was more upon not having a develop and production environment and only a production environment for client work which automatically pulls from the master branch. (like the link posted above in my previous post)
I know and am sure that there are other workflows that you an choose from for git deployment.. just ignorant to them but we’ll learn!
@yeeyang – I understand, though I don’t agree that having “only a production environment” is ever a good idea.
I like the idea of using git for deployment. The distinction I’m making is that I would never work from the “hub” branch (the branch that is auto-deployed from). That’s effectively the same as working on the live site.
Work in a “dev” branch, test,test,test, and then push changes to the “hub” branch when you know everything is ready.
@mottie I like the idea that we can have “versioning” and different environments as stated above (development and production). But for a designer, it just seems completely made for developers, which isn’t a bad thing.
Are there any decent step by step tutorials (with a GUI)?