Skip to content
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

Curious why you renamed your fork #66

Open
daluu opened this issue May 2, 2018 · 2 comments
Open

Curious why you renamed your fork #66

daluu opened this issue May 2, 2018 · 2 comments

Comments

@daluu
Copy link

daluu commented May 2, 2018

I think the rename may have caused issue/PR references from your fork back to the original project's issues & PRs. Because as I recall forks don't normally do that, otherwise it'd look messy in Github.

Not that this is a problem, just curious as I noticed that looking at the original project's issues. Were you thinking this would be the superceding replacement to AutoPy? Like wrk2 is to wrk.

@paulie-g
Copy link
Owner

paulie-g commented May 2, 2018

To be perfectly honest, I don't remember. I have a vague recollection that I forked it, transferred the issues, and possibly applied some fixes. Although seeing as it is even with master, I'm either misremembering or I neglected to push them to github. At some point in this process, I lost the underlying use case and time being short..

As far as your actual question, the references you're talking about are a result of running an issue/pr transfer. Github has an api for it as I recall, although it has a number of problems.

@daluu
Copy link
Author

daluu commented May 2, 2018

Thanks for the clarification, didn't know about that API. You reminded me now that forks don't clone over the issues & PRs indeed, which you would have had to do with the API you mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants