“Learn from the mistakes of others.”
- Eleanor Roosevelt
Why mess up when you don’t have to? Learn from my mistake. Writing an article on how to set up organizations on GitHub for team projects is nothing to jump up and down about because it’s is pretty simple. It’s when you set it up wrong, there might not be problems right away, but as your team makes progress with pull requests and merges, it will get messy. Of course, this happened to me and my team. So let’s do it the right way.
On the top right between the alert bell and your icon click on the “+” and click “ New organization”.
If this is a fun project you are doing in a team, don’t sweat it. Pick the Free plan.
Fill out the information requested and verify your account to make sure you are somewhat a human. Click next.
This is where you can add the team members to the project. When finished, click “Complete setup”.
If the next page is a questionnaire, go ahead and fill it out if you like. I just ignored it and clicked “Submit”. Now you should see this page.
Get team members to approve the project invite email. Once that is done, their info should all be in the “People” section. Then click on “Create a new repository”.
Fill out the required fields. Since this is a free tier, make sure to click on “Public” so team members can request and approve pull requests and merges. Click on “Create repository” when finished.
Team members should follow these steps on the CLI and everyone will be all set to go.
It’s that simple. For organizations members can clone instead of forking.
If you enjoyed this article and would like more info on GitHub or Git leave a comment below and let me know. Maybe my next article can be on setting up permissions and pull requests.