• # February 14, 2013 at 4:03 pm

    Hello guys,
    is there a possibility to automatically push the changes made in folder to github, without committing it manually ?

    Thanks for your help :)

    # February 14, 2013 at 4:31 pm

    Sounds like a bad idea, to me.

    # February 14, 2013 at 7:21 pm

    If you realize that you have a bad habit, why are you trying to preserve it? Why try to make git work exactly like live editing, when live editing is what you’re trying to avoid?

    @JoshBlackwood has the right idea with commit messages.

    # February 14, 2013 at 11:18 pm

    If you’re not afraid to break something, then you may want to utilize Git for deployment.

    I’m pretty much doing this for my own site (because I’m not overly concerned if it breaks) but for client sites, I definitely would NOT take this approach.

    [Using Git for Deployment]( “Using Git for Deployment”)

    For client or work-related work, I would do a master branch, develop branch, and then feature branches to do edits and updates with.

    Full Disclaimer: I’m a newb with Git (only 3 weeks in) but I feel like I have a pretty good grasp of the basics. Still lots to learn but I’m starting to get it.

    # February 15, 2013 at 12:32 am

    @yeeyang – there’s no reaosn to avoid deployment with git. The point is, that normal commits shouldn’t *automatically* be pushed to the production environment.

    For example, you might have a master branch, a production branch, and a development branch.

    When you start working on something, you’d fork from the development branch, and then push back when you’re done.

    Once you’ve completed testing and you’re sure everything works fine, push the development branch to the master, and from there to the production branch (i.e., the live site).

    # February 15, 2013 at 12:42 am

    Damn. Git sounds so much more complicated than I initially thought after reading this.

    # February 16, 2013 at 4:30 pm

    @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

    # February 16, 2013 at 8:34 pm

    …and, if you forget something, [references abound](

    # February 16, 2013 at 8:51 pm

    @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!

    # February 17, 2013 at 12:09 am

    @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.

    # February 17, 2013 at 12:14 am

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

    # February 17, 2013 at 1:14 am

    @chrisburton – might check out [this article](

    # February 17, 2013 at 6:19 am

    @traq @joshuanhibbert Appreciate it, guys. Reading them now.

    # February 17, 2013 at 2:19 pm

    @chrisburton – I’m a *huge* fan of Tower:

    # February 17, 2013 at 2:26 pm

    Or check out, that’s pretty much the same for free

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic.