GitHub Collaboration
If someone invites to a GitHub repo for a collab.
Then also, do we need to create a separate branch and make a pull request or directly commit to the main branch?
3 Replies
generally, if you're working on a busier code base, you assign one or two people to be allowed to merge into main, then the rest submits pull requests that get approved by them and then merged. Or even with another layer of abstraction, where main only gets updated with releases, development is guarded by a small number of people and only available through pull requests
for quieter systems, you can get away with just having everyone commit straight onto whatever branch you want, though I'd still recommend protecting main and only letting people merge into it, it prevents accidental commits when someone forgets to switch to dev or open a feature branch
does that answer your question?
We are the team of 17 members, each member has to write a report of the work they did. For each individual, sub folders have been created to update work status. I've to work on my folder, so do I need to make a pull request?
So this isn't a coding project?
"need to" is all relative. There is no one way to work with git. If everyone has their own folder that they work in, I'd say it's probably not that useful to use pull requests though. Especially if it's not a coding project where integrity across the entire repo is super important