Added instructions for updating remote repositories after name change. #29

Merged
merged 2 commits into from Oct 10, 2012

Conversation

Projects
None yet
3 participants
@ryanstewart
Contributor

ryanstewart commented Oct 9, 2012

No description provided.

@ppicazo

This comment has been minimized.

Show comment Hide comment
@ppicazo

ppicazo Oct 9, 2012

Contributor

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: git@github.com:ppicazo/Source-Code-Pro.git

They should only set the new remote url on the remote which is pointing to the adobe fork.

Contributor

ppicazo commented on README.md in 5f59284 Oct 9, 2012

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: git@github.com:ppicazo/Source-Code-Pro.git

They should only set the new remote url on the remote which is pointing to the adobe fork.

@miguelsousa

This comment has been minimized.

Show comment Hide comment
@miguelsousa

miguelsousa Oct 9, 2012

Owner

Paul, does that mean that Ryan's instructions need to be revised?

Owner

miguelsousa commented Oct 9, 2012

Paul, does that mean that Ryan's instructions need to be revised?

@ryanstewart

This comment has been minimized.

Show comment Hide comment
@ryanstewart

ryanstewart Oct 9, 2012

Contributor

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.

Contributor

ryanstewart commented Oct 9, 2012

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.

miguelsousa added a commit that referenced this pull request Oct 10, 2012

Merge pull request #29 from adobe/readme-update
Added instructions for updating remote repositories after name change.

@miguelsousa miguelsousa merged commit e97ff6d into master Oct 10, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment