gogs team used the second method is as follows, with reference to the previous approach to the previous method:
New by the root user organization, such as the establishment of hardware, then the team's technical director pulled the owners of this team inside. What happened afterwards has a team of technical people in charge to deal with.
And team technical director login account, and then do the actual invite technical personnel of each module.
There are technical team responsible for the establishment of warehouses actual production use.
Add the appropriate person in charge of the technical staff needed in the production of the warehouse.
Push protection on the main branch, only the white list can be pushed inside the personnel master.
After the warehouse set up, empty warehouse, into the appropriate mask setting file by the person in charge, do first the first commit, the establishment of the master branch.
- After pulling the data and technical personnel, first create their own dev branch, and then developed in the dev branch above, and push.
git branch dev // 创建分支
git checkout dev // 切换分支After completing the stage:
git add . // 当前文件夹下所有加入追踪
git commit -m "更新说明" // 编写本次更新的更新说明
git push origin dev // 推送到相应的远程分支- After the person in charge of the latest files pulled down, merge dev branch to master it, and then again and again to master it.
git checkout master
git merge dev
git push origin master