I think the problem was what happens with the PR in Githubs user interface.
This question was asked many times, answer is simple: NO you can't move over Pull requests to different repositories on Github! It's also impossible to export and reimport them. People have to recreate them. Dawid is correct: You can merge the pull request also into another rlocal repository, but this is impossible with the Github UI. So basically, you have to read the email that comes in with the Pull Request that lists the link to the branch and patch. Then use git command line (or Tortoise) and copypaste the URL there as "source branch" for the merge. Then you execute the merge, squash and commit/push. Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Dawid Weiss <[email protected]> > Sent: Monday, March 8, 2021 3:25 PM > To: Lucene Dev <[email protected]> > Subject: Re: Repository fork (master) about to happen (Wednesday) > > > What happens to open PRs? > > A pull request on github is essentially a diff between two commits. > Existing PRs have to be placed on top of the new development branch. > Note these repositories are (initially) identical with lucene-solr so > if somebody clones the solr repo and the solr-lucene repo, they can > create the same PR over at the new project (pointing at the new main > branch as a reference). > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
