gitlab權限基礎知識
① 可見性（庫類別）
私有庫：只有被賦予權限的用戶可見
內部庫：登錄用戶可以下載
公開庫：所有人可以下載
———————————————————————————
② 成員權限說明
Guest(匿名用戶) - 創建項目、寫留言薄
Reporter（報告人）- 創建項目、寫留言薄、拉項目、下載項目、創建代碼片
段
Developer（開發者）- 創建項目、寫留言薄、拉項目、下載項目、創建代碼
片段、創建合併請求、創建新分支、推送不受保護的分支、移除不受保護的分
支 、創建標籤、編寫wiki
Master（管理者）- 創建項目、寫留言薄、拉項目、下載項目、創建代碼片
段、創建合併請求、創建新分支、推送不受保護的分支、移除不受保護的分
支 、創建標籤、編寫wiki、增加團隊成員、推送受保護的分支、移除受保護
的分支、編輯項目、添加部署密鑰、配置項目鉤子
Owner（所有者）- 創建項目、寫留言薄、拉項目、下載項目、創建代碼片
段、創建合併請求、創建新分支、推送不受保護的分支、移除不受保護的分
支 、創建標籤、編寫wiki、增加團隊成員、推送受保護的分支、移除受保護
的分支、編輯項目、添加部署密鑰、配置項目鉤子、開關公有模式、將項目轉
移到另一個名稱空間、刪除項目
如果是開發人員選擇Developer即可，只是查看權限，選擇Guest即可
③ Protected Branches
(1) 四個作用
- it prevents its creation, if not already created, from everybody except users with Maintainer permission
- it prevents pushes from everybody except users with Maintainer permission
- it prevents anyone from force pushing to the branch
- it prevents anyone from deleting the branch
Note: A GitLab admin is allowed to push to the protected branches.
(2) 更加精細的設置：
Using the “Allowed to push” and “Allowed to merge” settings, you can control the actions that different roles can perform with the protected branch. For example, you could set “Allowed to push” to “No one”, and “Allowed to merge” to “Developers + Maintainers”, to require everyone to submit a merge request for changes going into the protected branch. This is compatible with workflows like the GitLab workflow.