Thanks for the reply Dustin. I have a quick noob question though: if I have multiple branches and I changed something in the master branch, can I make that change apply to all the other branches?
On Oct 12, 5:38 pm, Dustin <[EMAIL PROTECTED]> wrote: > On Oct 12, 12:15 am, AtsoK <[EMAIL PROTECTED]> wrote: > > > Hello! > > > I never thought I'd need to deal with version tracking, but after > > having a live website, I'm thinking I should. > > > Say I have a feature I need to implement, but it could take days or > > weeks to finish. Meanwhile, there's a tiny bug I could fix and deploy > > in one minute. I find that I'm making whole duplicates of my site on > > my local machine with the feature(s) I'm working on, and deploying the > > original copy to my server, if I ever need to make changes. > > > This is kind of a pain, so I'm wondering if Git can make this easier > > for me? Thank you! > > Absolutely. You've just described a very common workflow. > > You can have multiple sets of small and large features you're working > on, the most current version of the site, and every version that's > ever shipped all at the same time. Then you have simple tools for > moving those changes around and seeing which changes are in which > places. > > I couldn't imagine working without it. :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
