▲ 2268 ▼ Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft. (programming.dev) submitted 1 year ago* by Tea@programming.dev to c/technology@lemmy.world 279 comments fedilink hide all child comments Post New Git Repo.
[–] twice_hatch@midwest.social 29 points 1 year ago (2 children) The issue tracker is usually the concern permalink fedilink source parent hideshow 4 child comments replies: [–] lemmydividebyzero@reddthat.com 4 points 1 year ago (1 child) Yeah, that was my point in the first comment... But not only that... The development with multiple people is decentralized, yes... But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don't have an account on each of these... Try pushing code or making a pull request and see how it fails, because you are not authenticated... permalink fedilink source parent hideshow 2 child comments replies: [–] xigoi@lemmy.sdf.org 0 points 1 year ago* SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it. permalink fedilink source parent [–] xigoi@lemmy.sdf.org 2 points 1 year ago (2 children) How would decentralization work for an issue tracker? The issues have to be stored somewhere. permalink fedilink source parent hideshow 4 child comments replies: [–] WhyJiffie@sh.itjust.works 4 points 1 year ago naturally on the instance that hosts the repo permalink fedilink source parent [–] pinball_wizard@lemmy.zip 2 points 1 year ago The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances. permalink fedilink source parent
[–] lemmydividebyzero@reddthat.com 4 points 1 year ago (1 child) Yeah, that was my point in the first comment... But not only that... The development with multiple people is decentralized, yes... But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don't have an account on each of these... Try pushing code or making a pull request and see how it fails, because you are not authenticated... permalink fedilink source parent hideshow 2 child comments replies: [–] xigoi@lemmy.sdf.org 0 points 1 year ago* SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it. permalink fedilink source parent
[–] xigoi@lemmy.sdf.org 0 points 1 year ago* SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it. permalink fedilink source parent
[–] xigoi@lemmy.sdf.org 2 points 1 year ago (2 children) How would decentralization work for an issue tracker? The issues have to be stored somewhere. permalink fedilink source parent hideshow 4 child comments replies: [–] WhyJiffie@sh.itjust.works 4 points 1 year ago naturally on the instance that hosts the repo permalink fedilink source parent [–] pinball_wizard@lemmy.zip 2 points 1 year ago The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances. permalink fedilink source parent
[–] WhyJiffie@sh.itjust.works 4 points 1 year ago naturally on the instance that hosts the repo permalink fedilink source parent
[–] pinball_wizard@lemmy.zip 2 points 1 year ago The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances. permalink fedilink source parent
