nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqcmgqvz7xr07euwkum3mjghjqcu4d3k2fcyf6g4uwwe5ggnd6fetqn0jpfa (nprofile…jpfa) Hmm, you could probably script it, though. Moving the code is a matter of pulling it all down, removing the remote, adding the new remote (to e.g. GitLab or BitBucket or whatever), and pushing again.
Physically creating the repo in the new place could probably also be done programmatically, depending on the API support of the service you're moving *to*.
Moving PRs and Issues and Releases... yeah, that could be tricky. You can obviously access all that stuff using the GitHub API, but what to do with them? Releases maybe, you could simply create in the new system. Maybe Issues/Discussions too. But PRs? Hmm, could be tricky.
Graham Downs /
npub1q8…a5w8f
2025-05-20 11:08:26
in reply to nevent1q…yxvs
Author Public Key
npub1q8hnju2crm5r4fu7ystcdfav2r8etmx45nsur4le5ljjmhwj5yzs9a5w8fSeen on
wss://relay.mostr.pubPublished at
2025-05-20 11:08:26Event JSON
{
"id": "be575d43b70f5e09321371477cbcc023e0692d213a3d2b56471da9f5d263264d",
"pubkey": "01ef3971581ee83aa79e241786a7ac50cf95ecd5a4e1c1d7f9a7e52dddd2a105",
"created_at": 1747739306,
"kind": 1,
"tags": [
[
"p",
"c6d0060bc61bfd9e3adcdc77245e40c72ad8d949c113a4578e7668844dba4e56",
"wss://relay.mostr.pub"
],
[
"p",
"118cd39da270a800372ab7276a46b488cca3c40dd2b34f73b857fc8f72fae0f8",
"wss://relay.mostr.pub"
],
[
"e",
"9a4ac750fb715260abb436a6642464288565d9cdfe928fcc9c3263df01aa020e",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.africa/users/GrahamDowns/statuses/114539843164254144",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqcmgqvz7xr07euwkum3mjghjqcu4d3k2fcyf6g4uwwe5ggnd6fetqn0jpfa Hmm, you could probably script it, though. Moving the code is a matter of pulling it all down, removing the remote, adding the new remote (to e.g. GitLab or BitBucket or whatever), and pushing again.\n\nPhysically creating the repo in the new place could probably also be done programmatically, depending on the API support of the service you're moving *to*.\n\nMoving PRs and Issues and Releases... yeah, that could be tricky. You can obviously access all that stuff using the GitHub API, but what to do with them? Releases maybe, you could simply create in the new system. Maybe Issues/Discussions too. But PRs? Hmm, could be tricky.",
"sig": "587f8c1cfe6f845b1c073d754300c6a22b7c6999e1ad99a2ca09e48a0bbcd10d0d30e6fbdceccabb37c54d9f95199b58989587cfb408ab9d190b1ccba72d467d"
}