@b0rk another deep arcana is changing remote URLs - I memorized this years ago when teaching H.S. kids who would often miss the “fork” step of an assignment and had cloned the template repo instead of their own copy.
Top-level
3 comments
@stormsweeper that's the right way to do it. Pre-emptive forking is only a thing because GitHub want to exploit the same network effect that social media companies were milking, so they decided to force every prospective contributor not just to create a superfluous fork, but insist that it be hosted on GitHub, too, and use their proprietary PR system. @stormsweeper in a more perfect world, you'd clone the original, make your changes, and just submit that (a patch). But GitHub refuses. Can't grow the garden that way. |
@b0rk more recently, have used this to move a repo fully from bitbucket to GitHub