You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: