Ensure all open comments are resolved before allowing code change merging

高レベル 1手動レビューsupply-chain

説明

Organizations should enforce a “no open comments” policy before allowing code change merging. In an open code change proposal, reviewers can leave comments containing their questions and suggestions. These comments can also include potential bugs and security issues. Requiring all comments on a code change proposal to be resolved before it can be merged ensures that every concern is properly addressed or acknowledged before the new code changes are introduced to the code base. Note Code change proposals containing open comments would not be able to be merged into the code base.

チェック方法

監査方法: 手動レビュー

この推奨事項は自動ではチェックできません。--include-manual を指定すると、スキャン結果にこの手順付きで一覧表示されます。

For every code repository in use, verify that each merged code change does not contain open, unattended comments.

修正方法

修正方法: ガイダンスまたは IaC パッチ

For each code repository in use, require open comments to be resolved before the relevant code change can be merged. 10 CIS Software Supply Chain Security Guide

プロパティ

オペレーティングシステム: すべて
タグ: devsecopssupply-chain
参照: CIS Software Supply Chain Security Guide Benchmark v1.0.0 - 1.1.11 Ensure all open comments are resolved before allowing code change merging