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?

  • How to determine when a Git branch was created?
  • What do these words mean in Git: Repository, fork, branch, clone, track?
  • How do I create a new git branch from an old commit?
  • How do I make git-svn use a particular svn branch as the remote repository?
  • Git change history of feature-branch into a new branch?
  • How can I push a new branch?
  • What's the easiest way to merge all but one change from a branch in Git?
  • Branch descriptions in git, continued
  • Checkout branch on different remote
  • How to update my working Git branch from another branch (develop) ?
  • Automatically rebase gerrit Changes
  • When is the right time to delete a git feature branch?
  • 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.