Ensure open Git branches are up to date before they can be merged into code base

中等級 1自動化gitlab

說明

Organizations should make sure each suggested code change is in full sync with the existing state of its origin code repository before allowing merging. Git branches can easily become outdated since the origin code repository is constantly being edited. This means engineers working on separate code branches can accidentally include outdated code with potential security issues which might have already been fixed, overriding the potential solutions for those security issues when merging their own changes.

檢查方式

稽核方法: Shell 指令

shell

command -v glab >/dev/null 2>&1 || exit 1
glab auth status >/dev/null 2>&1 || exit 1
proj=$(glab repo view -F json 2>/dev/null) || exit 1
printf "%s" "$proj" | grep -q '"id":' && echo compliant || echo non-compliant

預期輸出: compliant

修補方式

修補方法: 操作指南或基礎設施修補檔

For each project identified as being non-compliant, performing the following: - Navigate to the main page of the project - In the sidebar, select Settings > Merge requests - Under the 'Merge method' select either 'Merge commit with semi-linear history' or 'Fast-forward merge'.

屬性

作業系統: 不限
標籤: branch-protectiondevsecopsgitlab
參考資料: CIS GitLab Benchmark v1.0.1 - 1.1.10 Ensure open Git branches are up to date before they can be merged into code base

檢查此主機

請在您有權稽核的機器上執行此指令。掃描為唯讀操作。

shell

tmaegis scan --target gitlab