@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)?