There are three ways to collaborate on GitHub:
First, Fork Way
More ways to introduce online (more large open source projects, such as Cocos2d-x)
The developer forks himself to create a separate branch, completely independent from the main branch, and after the pull code, the project maintainer can determine whether the merge code is based on the quality of the code
This way online method is more, here is not detailed description
Second, the organization
An organization's owners can establish teams of different access rights for different code warehouses.
Accounts Settings + Organizations =>create new organizations create a new organization and add project members, as prompted.
Create a new repository and enter repository settings =>collaborators under teams Click on the organization you just created, like Eveloper-51/owners
Inside, you can add or remove members of your organization.
Third, collaborators
The owner of the code warehouse can add collaborators with read-only or read-write permissions to a single warehouse.
The partner way is more practical, also very convenient, a new repository, after completion, into the repository settings, and then in manage collaborators can manage collaborators.
Other collaborators, utility ssh-keygen-c "[email protected]" (here email uses GitHub account) to generate public and private keys, in accounts settings= ssh keys to upload the public key.
After uploading, you can use the tower (Mac git admin tool) clone remote Repository to log in using SSH (where the private key is used) so that other collaborators can push the code normally.
Reference URL:
http://xiaocong.github.io/blog/2013/03/20/team-collaboration-with-github/
Http://blog.leezhong.com/tech/2011/02/25/git-workflow-with-blog-demo.html
Http://www.yangzhiping.com/tech/github.html#q1
There are three ways to collaborate on GitHub: