Thanks Mathew.
I am good with git on my local repo. I long ago updated its remote
origin to be TracksApp/tracks. I can push / pull commits between my
local repo and my github repo no problem.
My issue is my github repo still says it is a fork of bsag/tracks, not
TracksApp/tracks. The github TracksApp/tracks page says it is also a
fork of bsag/tracks. The "fork" button says my fork so it won't let me
fork it again. They don't seem to expose the .git directory on Github
(probably won't be a good idea either!)
So far, my only thought would be to delete my github fork entirely from
my account and then fork it again, but that seems rather drastic. Plus,
I assume that would mess with my history of github pull requests...
I looked through help.github.com. We probably should have done a
"Transfer Ownership" from bsag to TracksApp when TracksApp was
established. Then if bsag wanted to she could fork it back again into
her github account. Since TracksApp already has a fork in it, the
http://help.github.com/move-a-repo/ says we would need to get github
support involved to make the change at this point.
At this point, I am ready to let it go. All it means in a practical
sense is that when I want to do a pull request, I have update the base
branch from bsag to TracksApp...
On 01/16/2012 02:41 PM, mathew wrote:
...and if you've forked Tracks into your own tracks repo on github and
need to reparent that to TracksApp/tracks, the answer should be to
make a similar change to the upstream URL, as per
http://help.github.com/fork-a-repo/
Both URLs are just entries in .git/config in the project directory, so
you could just edit that file with a text editor and change the URLs
that way.
Fundamentally, Git doesn't care much about where it pulls from—it just
looks up the URL in the config, goes there, and downloads all the
objects with hashes it doesn't already have. Since the hashes are
based on content, the historical trunk ones will be the same whichever
upstream Tracks repo you were using, so it should just be a matter of
changing where Git goes to get updates or upstream updates.
I found<http://newartisans.com/2008/04/git-from-the-bottom-up/> very
helpful when getting to grips with it.
mathew
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
