Decouple repo from pennylane-qrack fork

[nathanshammah]

Currently, the unitaryfund/pennylane-qrack repo is a fork of pennylane/pennylane-qulacs. See here:

I thought this would not be an issue, but actually it can become a bit annoying since as a user, I cannot fork this repo directly, since I already forked pennylane/qulacs. Also, while modeling this repo on the qulacs plugin made sense to get started, they are different repositories now.

Note that to do it, we would basically need to delete this repo. One can keep commits, but issues and PRs would be removed, see here: https://stackoverflow.com/questions/29326767/unfork-a-github-fork-without-deleting/41486339#41486339

Thoughts? @WrathfulSpatula @josh146 @cosenal @natestemen @vprusso @dime10

[josh146]

Ah, that's a good point. It's a bit annoying to lose issues and PRs, but I think it makes sense to create a new repository.

[WrathfulSpatula]

We'll wait for other feedback from those tagged, but it's not hard to do this. I see your point, and the upstream repository is probably sick of the PRs I occasionally accidentally open on their fork instead of this one, before I realize my mistake.

[natestemen]

It looks like you can make a support request to detach this fork from the pennylane-qulacs without loosing the GitHub metadata (issues, PRs, wiki, etc) using https://support.github.com/request/fork then choosing "detach a fork".

[cosenal]

I created a support request following the link that @natestemen shared. The support ticket is at https://support.github.com/ticket/personal/0/2841472, but you probably don't have access to see it. I will keep you posted in this thread.

[cosenal]

Thanks to Nate for the tip, and Travis from Github Support, the fork is now detached. Please reopen if you spot any issue with the detachement.