@vegetaaaaaaa@lemmy.world to Selfhosted@lemmy.worldEnglish • 7 days agoOrganic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.programming.devimagemessage-square39fedilinkarrow-up11arrow-down10file-textcross-posted to: technology@lemmy.worldtechnology@lemmy.world
arrow-up11arrow-down1imageOrganic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.programming.dev@vegetaaaaaaa@lemmy.world to Selfhosted@lemmy.worldEnglish • 7 days agomessage-square39fedilinkfile-textcross-posted to: technology@lemmy.worldtechnology@lemmy.world
cross-posted from: https://feddit.org/post/9959466 geteilt von: https://programming.dev/post/27692275 Post New Git Repo.
minus-square@jagged_circle@feddit.nllinkfedilinkEnglish0•edit-27 days agoThis is the benefit of using distributed tools like git.
minus-square@rice@lemmy.orglinkfedilinkEnglish0•6 days agoYea tons of devs treat all of these platforms like the central host, but you can host it on all of them at once lol
minus-square@mac@lemm.eelinkfedilinkEnglish0•6 days agoWonder if there’s a tool for compiling all issues from seperate sources to allow devs with repos hosted on several different platforms to respond easier. Also feels like a way to get repeat issues more frequently
minus-square@jonne@infosec.publinkfedilinkEnglish0•edit-27 days agoYeah, the code history is the easiest thing to migrate. The other stuff like issues relies on having a good exporting/importing tool on both sides.
This is the benefit of using distributed tools like git.
Yea tons of devs treat all of these platforms like the central host, but you can host it on all of them at once lol
Wonder if there’s a tool for compiling all issues from seperate sources to allow devs with repos hosted on several different platforms to respond easier.
Also feels like a way to get repeat issues more frequently
Yeah, the code history is the easiest thing to migrate. The other stuff like issues relies on having a good exporting/importing tool on both sides.