Repository with temporary issues

[ghost]

Hello everyone,

I've accepted pull request #17, but it added quite a lot of weight to the repository (it's now around 20 MB). I was able to revert the changes, but the old files remain in the history. I don't know how to erase the commits AND their files.

I asked a question on StackOverflow, and I'm still trying to solve this issue:
http://stackoverflow.com/questions/14264719/how-to-completely-remove-a-merged-pull-request

For now, I will not accept any pull requests to avoid increasing the mess. And please, try not to base new pull requests on this code. I'm trying to solve this ASAP. Sorry for the inconvenience...

For users, feel free to clone and use RouteFlow. It doesn't affect the functionality.

If anyone has any tips, they're more than welcome :)

[joestringer]

Hi Allan,

You can do this by force-pushing the older version. This is generally a bad idea, but I think in this case it is excusable if not many have been using this latest master.

Steps:-

• Check out the older version (I think you want version 70b29ba ?)
• git push --force origin HEAD:master
  (where 'origin' is the name of this remote repository)

This will clean up the master repository. In future it is probably best to only merge locally and push to GitHub when you are sure you want to share the changes.

[ghost]

Thank you very much Joe! It worked perfectly.

I know this would normally be a serious offense. I used GitHub's automerge on impulse, and then it was too late...