By pure I mean don’t have code in a remote repository that does not work, but if I keep it in a local one is is not an issue Surrey if I run a migration and then delete the branch the migrations table will be out of sync. I guess the answer is to be more careful:). I guess backing up the DB first is another strategy.
On Wednesday, September 6, 2017 at 4:31:57 PM UTC+1, Hassan Schroeder wrote: > > On Wed, Sep 6, 2017 at 1:07 AM, Ben Edwards <lo...@funkytwig.com > <javascript:>> wrote: > > > On the git front I don’t tend to commit stuff that does not work but I > guess > > if I create a local branch for stuff and don’t commit it remotely I can > > delete the branch and keep my remote git pure(ish) but the rails > database > > would still be unconsistent, or should I use a efferent git workflow. > > "pure"? In general you'll be best off always working in a feature > branch and making frequent commits, especially for things like > migrations that have side effects. > > And you can delete remote branches as well as local ones, so... > > -- > Hassan Schroeder ------------------------ hassan.s...@gmail.com > <javascript:> > twitter: @hassan > Consulting Availability : Silicon Valley or remote > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/d6ba86f7-29e8-46e3-bd90-fd8006db7c0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
