Configuration for collaborative development by multiple users on GitHub

Configuration for collaborative development by multiple users on GitHub

Configuration for collaborative development by multiple users on GitHub

GitHub For Windows: https://windows.github.com/

The basic logon registration is not detailed.

In terms of source code management, the most important thing is the warehouse. The concept of warehouse is easy to understand. The so-called warehouse is the place to store things, because the warehouse is the place where we store the source code.

After GitHub is downloaded and installed, A + symbol is used in the upper left corner to create and migrate the repository. right-click the repository and choose Open in Explorer to Open the project in file resource manager.

When we modify the project (add files, modify files, delete files, etc.),

, Fill in the corresponding record information, and then click Sync in the upper right corner to synchronize to GitHub.

The rest will not be introduced much. Today's topic is the configuration of collaborative development by many people. This configuration is mainly configured on the GitHub website.

Configure multi-person collaboration: Create an organization> create a repository> Create a branch> Create a team> invite teammates

Log on to Github, click your user name in the upper left corner, and a drop-down box will be displayed. Click Create orangization, and enter the Organization name and email address. If it is public, the following billing process will be ignored.

Creating a repository is not mentioned here

After creating a repository, you need to create a branch. The main purpose of the Branch is not to affect the main version. as a common example, a main version of my project has been released, but the user has reflected some opinions or bugs, so we have to avoid affecting the current version, modify it because we need to create a BUG Branch, which will be operated based on the source code of the current version. of course, we can create a branch for developers to avoid affecting the main version. after creating the branch, click Setting on the right hand side to set the branch as the default branch.

Then, create a Team. By default, a Team named Owners is created when an organization is created. This Team has the maximum administrator privilege and cannot be modified, by default, a member is the creator of the organization, that is, yourself. then you can click Create New Team below to Create a New Team. the Team has three permissions: Read Access (Read-only), Write Access (readable and writable), and Admin Access (Administrator permission). The default Owners is the Admin Access permission.

Invite comrades-in-arms and click to enter the team.

Enter the name of the comrade-in-arms to be invited, and then you can send the invitation to the comrade-in-arms. You only need to agree with the comrade-in-arms and then add it for joint development.

On the GitHub client, Merge the branches. Click the drop-down menu of the branches, Click Manage to enter the management module of the branches, and drag the corresponding branches to the Merge module below, as shown in figure

The above is the incept of the younger brother, and the record is too detailed. It provides some minor help for the GitHub users who just got started and a part of the open-source community. this is not detailed. I will sort out a complete document and release it later.

GitHub Tutorials:

Create a personal technical blog via GitHub

GitHub tutorials

Git tag management details

Git branch management

Git remote repository details

Git local Repository (Repository) Details

Git server setup and Client installation

Git Overview

Share practical GitHub tutorials

GitHub details: click here
GitHub: click here

This article permanently updates the link address: