Associate git repo with existing fork network

Question

Using GitHub Enterprise, I forked a private repo. I then made the upstream repo public, which broke the 'fork' relationship between the public upstream and my private personal fork (as noted here). I've now also made my copy of the repo public. As far as I can tell, I can no longer make pull requests from my copy of the repo to upstream, because my copy is not recognized as a fork of upstream.

Can I re-associate my repo with the upstream repo as a fork?

This is probably something you should take up with GitHub Enterprise support. — nwinkler, Jun 17 '15 at 15:28

score 2 · Accepted Answer · answered Jun 17 '15 at 15:45

2

GitHub support has removed fork relationships for me before, so I suspect they'd also be able to reattach you.

To do it on your own, I'd:

Make a new fork of the upstream repo
Change your personal fork's origin to the new fork

You'll lose GitHub history for your current fork (Pull Requests, etc.), but you'll be able to work with upstream again.

answered Jun 17 '15 at 15:45

Kristján

18,165
5
50
62

3

I wanted to avoid losing the history. GitHub Enterprise admins were able to reinstate the relationship. – Ben Mordue Jun 19 '15 at 08:15

Associate git repo with existing fork network

1 Answers1

Linked