4 ms·
Hmmm... I never finished updating my Github Sponsor thing, so I've just done that. But as someone that tended to create orgs for projects rather than have it a
by buro9 4y ago
Hmmm... I never finished updating my Github Sponsor thing, so I've just done that.
But as someone that tended to create orgs for projects rather than have it all under a personal account, should I move all of the projects? I guess so, right?
What's the recommended way to move Go repos without breaking them for all users? (I have low-thousands of stars, but the largest project is used by mid-thousands of projects - so I anticipate breakage for my hopeful $5 one-off solo sponsor).
Something like using a vanity import path for all projects? https://sagikazarmark.hu/blog/vanity-import-paths-in-go/ https://sagikazarmark.hu/blog/vanity-import-paths-in-go/
- cdrini 4y agoI'm not entirely sure, but I think if your personal account is marked as a maintainer for the repo, it doesn't matter if the repo is under its own org? I feel like most projects create org accounts, so would be kinda surprised if that wasn't supported somehow.
- buro9 4y agoYeah, but then I'd need to create and maintain a lot of org accounts.
- cdrini 4y agoHmm I'm not sure I understand. Here's what I'm assuming: You currently have some number of org repos; eg: my-project/my-project, foobar/foobar And you have your personal account: buro9. You use your personal account to commit and maintain those org repos. As long as you set your personal account as an admin/maintainer on those org repos, I think you get all the benefits you need? I don't think there's any benefit to moving eg my-project/my-project to buro9/my-project
- Latty 4y agoThe .github/FUNDING.yml file in the repo determines who will be shown as people to sponsor, it's not related to the account or org that controls the repo.