-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support moving PRs #114
Comments
@alanjds Thanks for the feedback, but you'll have to explain further why PRs should be cloned. In my mind, a PR is intrinsically tied to the repo from which it was created. If I make a PR for |
Exactly. I am, with some more people, hard-forking https://github.com/google/grumpy to https://github.com/grumpyhome/grumpy because the former stalled. There, 21 PRs full of comments got left without following answers. I want to clone this all to the new repo that inherits the same base one, then fix/review the PRs and merge some of it. |
I understand. I'll have to do some looking but I don't think this is necessarily complex. Kamino doesn't currently clone comments on even issues right now, so that will be another thing to consider. I'll tag this as investigating, but if you or anyone else wants to tackle it with a PR, that's fine as well. Otherwise, I'll start the initial work on it as I have time. |
Thanks for answering. To be transparent, Javascript is not my main language. For a bulk transfer as I need, maybe https://github.com/IQAndreas/github-issues-import suites better. Anyway, lets see what the other Grumpyhome devs says. |
Kamino cloned this issue to zhongweili/CardsWriting |
I would expect PRs to be moved also, not only issues.
The text was updated successfully, but these errors were encountered: