Ensure all open comments are resolved before allowing code change merging

VisokaNivo 1Ručni pregledsupply-chain

Opis

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.

Kako se proverava

Metod provere: Ručni pregled

Ova preporuka se ne može proveriti automatski. Skeniranje je navodi sa ovim uputstvima kada prosledite --include-manual.

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

Kako se ispravlja

Metod ispravke: Smernica ili zakrpa infrastrukture

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

Svojstva

Operativni sistemi: Bilo koji
Oznake: devsecopssupply-chain
Referenca: CIS Software Supply Chain Security Guide Benchmark v1.0.0 - 1.1.11 Ensure all open comments are resolved before allowing code change merging