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?

  • Remove a single merged branch from master branch
  • Git pull reverted commits in master?
  • With Git, how can I commit some changes in the working copy to a different branch?
  • git branch merging
  • git rebase --onto results on single commit
  • Does TFS branching have a child parent relation?
  • Git with SVN trunk and branches
  • Can you share a file and it's history between two git repositories?
  • Learning version control with git first or via SVN?
  • Unable to clone using Git over HTTP
  • How to clone Bitbucket repository when you have files?
  • Why does git am leave modified files lying around? How can I adapt my workflow to do better?
  • 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.