Fork Your Application's Data (Not Just Your Code)

Re:Fork Your Application's Data (Not Just Your Code) by atomical on Thursday November 08, 2012 @05:04PM (#4760132)

This isn't a setup issue. Don't work on more than one branch/feature at a time. It's a bad idea and not conducive to getting shit done.

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by samspot on Thursday November 08, 2012 @06:49PM (#4760539)

You act like we have a choice in the matter.

"Sorry, I can't look into your emergency production problem, I'm adding features to a blog."

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by eggbrain on Thursday November 08, 2012 @05:53PM (#4760328)

  Git checkout -b "feature-1"
  Git commit -am "Added feature 1, which included a migration"
  Git checkout -b "feature-2-that-builds-off-feature-1"
  Git commit -am "Added feature 2, which includes another migration"
  Git checkout master
  Broken (and with multiple migration files, even though I branched off for each new feature.)

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by grey-area on Friday November 09, 2012 @03:08AM (#4761857)

Have you considered branching the database along with your code?

[ Parent | on HN ]