No description provided.
Added instructions for updating remote repositories after name change.
Fixed line spacing.
I believe if the repository has been forked by a user, the name change will not occur on their fork.
For example, my fork will still exist at: firstname.lastname@example.org:ppicazo/Source-Code-Pro.git
They should only set the new remote url on the remote which is pointing to the adobe fork.
Paul, does that mean that Ryan's instructions need to be revised?
Yup, that's how I understand it as well, Paul, but if they've set up a remote repo to track any changes from the original repo (not the forked one) they'll have to change that as well.
Usually I've seen that called "upstream" which is why I referenced it there, and they'd have to change that upstream repo as well.
I'm basing my info off of this post - http://gun.io/blog/how-to-github-fork-branch-and-pull-request - which is where I got a lot of my git knowledge with regards to tracking changes from an original repo.
But if you think we can be clearer Paul, let me know.