My github repo is called Programming-iOS-4-Book-Examples, because it\'s the example code from my book \"Programming iOS 4\". Now I\'ve written a new edition of the book, retitle
In the end here's what I did:
I renamed the existing repo. This works great (thanks, github, for making that so easy). Don't forget to edit your own git repo's config
file to keep the remote branch relationship between your own master branch and the github repo's master branch.
I created a new repo with the old repo's name, consisting of nothing but a README.md providing the existing repo's new URL.
Thus, I didn't end up separating the iOS 4 book content from the iOS 5 book content. Instead, I rearranged the structure of the original repo and gave it a more general name, not tied to iOS 4 in particular. And existing links to the old repo don't break, because there's a placeholder repo at that URL, pointing to the new repo.