Gergely Nagy π
I will be moving my personal repositories from GitHub to my own Gitea instance. I just need to figure out a reasonable strategy...
I mean, I have a lot of repos on GitHub, a lot (about half of them) archived, never to be resurrected. Do I move them to my main account on Gitea, or to an archive account?
What do I do about repos that are obsolete, but are linked to from elsewhere? I can update my own links, sure, but what about links in packages? Do I add a README?
eloyesp
@algernon Just a personal note here, I don't like links to stop working, it happened so many times and I do not enjoy it... a pointer to the new place is the least bad thing I can think on...
For more on this approach: https://basecamp.com/about/policies/until-the-end-of-the-internet
Gergely Nagy π
Another problem: I have repos where I kind-of-moved off of GitHub already, and have a separate set of issues and PRs on Gitea.
As such, I can't migrate issues & PRs. Guess I'll just leave nuke the old (github) ones.
Gergely Nagy π
I'm tempted to go with the "screw it, I'm gone" attitude, and not leaving pointers behind. It's not like those things have many users or contributors or anything, and should still be reasonably easy to find at their new place.
Gergely Nagy π
There's 114 repos on GitHub under my name, 24 forked ones, 52 archived, 33 sources.
I made an initial attempt at cleaning up the archived ones, but only managed to delete 4.
I'll try a different approach: migrating over the obvious ones, and leaving things that I need to think about behind, for now.
However, the question still remains: what do I do with repos I migrated? Do I leave a mirror up? An empty repo with a README? Or nothing?
Gergely Nagy π
I suppose the first task would be to delete repos that aren't worth moving over. Like forks of stuff I used to contributed to, where the forks don't have any interesting, nostalgic, or historic value.
Gergely Nagy π
Oh dear, the amount of junk I have on GitHub is astonishing.
Gergely Nagy π
Organization migrated too, and only 22 repositories left. I'll tackle those some other day.
From 114 repos down to 22 in a couple of hours, I'll call that a success.
#Gitea's GitHub migration support is very, very, very nice.
Gergely Nagy π
Shoot! I have an entire organization to migrate too. But that's only 9 repositories.
Gergely Nagy π
21 archived ones, some of which will remain a bit on GitHub, because I need to update MELPA & similar with new URLs. Or just remove them from MELPA, to be honest, as they're archived.
Then there are 17 forks which I need to comb through and see what to do with them.
Gergely Nagy π
Down to 44 repos.
Only 6 non-archived sources, 3 of which I should transfer away to their new owners rather than keep them under my name.
Of the remaining 3: 1 can probably go, 1 needs a link updated, and the last one is algernon/algernon, for the README.
Phew.
Gergely Nagy π
The Org I migrated was the old #Chrysalis development organization, before it was rewritten in JavaScript and moved to keyboardio.
The issue tracker has some interesting gems, such as:
Gergely Nagy π
Repositories: 1.
Now it is really done.
Gergely Nagy π
Initiated the transfer of the last repo. Once accepted, the only one that remains will be algernon/algernon, a single README.md to show on my profile page pointing people elsewhere.
And with that, my #GiveUpGitHub project is complete.
Account remains, and I will still use GitHub for work. But anything personal, is not going there.
Gergely Nagy π
Of the four remaining repos, two have been transferred away to their new owner, and the last one I need to deal with, the new owner responded positively, but they need to delete their fork first.
Looks like my migration off GitHub will be done by the end of the week: no stars, no repos, no watches, no gists. Just work stuff left.
Gergely Nagy π
So, the last repository I want to transfer away is algernon/elfeed-goodies. It turns out, transferring is complicated!
If the new owner has a repo of the same name under their name, you can't transfer. If the new owner has a fork of the repository under their name, but with a different repository name, you can't transfer to them.
The only way to transfer a repository is if they delete their own fork, or ask GitHub support to detach it. Why that can't be self-service like delete, I dunno.
Gergely Nagy π
And with that, only 4 repositories left, 3 of them are waiting for people to respond back, and then they're getting transferred or migrated (& archived).
At that point, I will only have 1 repository under my name, with a single README to display on my GitHub profile.
I'll still be using GitHub, because of work, mind you.
Gergely Nagy π
Of the two, one is a Kaleidoscope fork, where I have a number of old, stale branches. I should probably save a copy of that as is, and then delete my fork.
The other is a Kaleidoscope plugin, where I have a pending PR open since 2018, last updated in 2020. I don't intend to maintain said plugin, so I'm inclined to just move it over and archive.
Gergely Nagy π
Pinged two people about the 3 repos that should be transferred. That leaves two repositories with their fate as of yet undecided.
Gergely Nagy π
Turns out, most of the forks I had were easily deletable. I used them for PRs, but the PRs have long been merged, and there was nothing useful left in the forks.
So I'm down to 6 total repositories, and by the end of the week, likely only one will remain.
Three needs to move to their new home (should've been done years ago), one has a PR I need to act on, and the last one has a lot of branches I need to review if its worth keeping.
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.