Deleting/“Rebasing” rails migrations

I’ve been working in a git branch on one portion of a rails site. I’ve made a lot of random changes to the schema while iterating, and I’ve made some migrations that revert previous migrations to add columns and things like that. Is it OK to delete redundant migrations like those (i.e. pairs of migrations that are just reverses of each other)? I don’t see why it would cause any problems because no one else is working on this branch, and the end result will be the same. Is there any chance of trouble if I go ahead with this?

  • Git branches & commits history after merge
  • What do these words mean in Git: Repository, fork, branch, clone, track?
  • Show Current Git Branch in Xcode 4.2
  • Switching branches without touching the working tree?
  • Subversion branch reintegration in v1.6
  • git: how do I merge between branches while keeping some changesets exclusive to one branch?
  • Which commit has this blob?
  • migrate from CVS to GIT without losing history
  • Git Integration to The Bug Genie?
  • Replay the last N git commits on a different branch
  • Git merge - manual merge - forcing conflic having WHOLE old and new file version
  • git rebase branch with all subbranches
  • One Solution collect form web for “Deleting/“Rebasing” rails migrations”

    There should be no problems, assuming you know perfectly good what to do and how to do it.

    But, you should ask yourself why you want to do this? It is no addition to your project. It only masks (some of) your iterations, which might be convenient to look back later to understand your working process or to explain it to someone else.

    Personally, I would just merge your branch with the main branch without deleting any changes at all. Nothing to be ashamed of right?

    Git Baby is a git and github fan, let's start git clone.