user.name, user.email must be your own account and email within the company. Generally, companies have internal personnel management systems, so just use this account name. Try to use a personal email within the company as well. Bar.
If your company has its own Git server, you can set the ssh public key of your computer so that you don’t need to enter your account and password every time when cloning. The code must have been pulled down using the git clone command. As for whether you have permission to the git warehouse, ask your leader.
Regarding Git branch management and what are the commonly used branches, I recommend you read this article: Git branch management strategy
3. How many branches does an average company have?
Comprehensive efficiency and cost
Projects with more than 2 people
Regarding the establishment of branches, a master branch is used for final release, a develop branch is the main development branch, and then each person has a feature branch for development tasks. After personal development and testing is completed, it can be merged into the develop branch. Release the beat version based on the develop branch.
Projects with less than 2 people
One master branch is used for final release, and one develop branch is enough. During development, all development is done directly on the develop branch
The main ones here are communication costs and management costs.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
user.name, user.email must be your own account and email within the company. Generally, companies have internal personnel management systems, so just use this account name. Try to use a personal email within the company as well. Bar.
If your company has its own Git server, you can set the ssh public key of your computer so that you don’t need to enter your account and password every time when cloning. The code must have been pulled down using the git clone command. As for whether you have permission to the git warehouse, ask your leader.
Regarding Git branch management and what are the commonly used branches, I recommend you read this article: Git branch management strategy
Projects with more than 2 people- Regarding the establishment of branches, a master branch is used for final release, a develop branch is the main development branch, and then each person has a feature branch for development tasks. After personal development and testing is completed, it can be merged into the develop branch. Release the beat version based on the develop branch.
Projects with less than 2 people- One master branch is used for final release, and one develop branch is enough. During development, all development is done directly on the develop branch
The main ones here are communication costs and management costs.