this post was submitted on 22 Sep 2023
39 points (97.6% liked)

Programming

17440 readers
226 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
39
How to handle collaborators on an open source project? (lemmy.ca)
submitted 1 year ago by [email protected] to c/programming
14 comments fedilink hide all child comments
 

What are some good rules to follow when handling people who want to collaborate on a project that is on your personal repo?

It looks like GitHub doesn't allow fine control of permissions unless it is an organization repo. I looked around and a lot of other projects (specifically browser extensions) still live on the main dev's account. I don't have any reason to doubt the people who want to help, but it might be nice to know what the best practices are.

Should I add everyone as a collaborator? This runs into the issue above where I can't limit permissions.

Should everyone push contributions from their forks? In that case, how would people work together on a particular feature.

you are viewing a single comment's thread
view the rest of the comments
[–] JackbyDev 3 points 1 year ago* (last edited 1 year ago) (1 children)

When opening a PR across forks there is an option to allow folks from the target repo to edit the branch. I don't know exactly what it allows but it should allow committing at least.

[–] [email protected] 2 points 1 year ago (1 children)

Neat. I'll check that out! Thanks!

[–] JackbyDev 3 points 1 year ago

Just fork any repo and make a random change and begin to open a PR. You don't have to actually open one to see the option.