Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossaryContacting Support and Reporting Bugs
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidanceDetermining Control Applicability
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: AzureAuto Checks: GCPAuto Checks: GitHubEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
GitHub Auto Checks Detailed Explanations
Ensure secret scanning is enabled to detect sensitive dataEnsure code owner approval is required for owned code changesEnsure at least two approvals are required before merging codeEnsure branches are deleted automatically after mergingEnsure unresolved conversations block mergesEnsure force push is disabled for all branchesEnsure admins are subject to branch protection rulesEnsure a CODEOWNERS file exists in the repositoryEnsure inactive repositories are archivedEnsure all required status checks pass before mergingEnsure linear history is enforced on the default branchEnsure branch protection is enforced on the default branchEnsure the default branch cannot be deletedEnsure vulnerability scanning is enabled for repository dependenciesEnsure public repositories include a SECURITY.md fileEnsure all organization members have MFA enabledEnsure only signed commits are accepted

Ensure unresolved conversations block merges

Framework Reference: A.8.25 (Secure Development Lifecycle) Integration: GitHub – Branch Protection

Why this matters

Requiring all review comments to be resolved before merging ensures that no reviewer feedback, bug report, or security concern is ignored.
Unresolved conversations often indicate unfinished discussions or unaddressed findings in a pull request.

By enforcing this setting, you ensure that:

  • Review feedback is acknowledged and resolved before code is merged
  • Code quality and security concerns are fully addressed
  • Peer review remains a meaningful control within your secure development lifecycle

Without this safeguard, unresolved feedback could be bypassed, leading to errors, vulnerabilities, or missed compliance issues.

What this check does

This check verifies that the branch protection rule for the repository has “Require conversation resolution before merging” enabled.
When active, GitHub blocks the merge of a pull request if any review comments remain unresolved.

How to fix it

From the GitHub Web Console

  1. Go to your repository on GitHub.
  2. Navigate to Settings → Branches.
  3. Under Branch protection rules, click Add rule or edit an existing one.
  4. In the rule configuration, scroll to Require conversation resolution before merging.
  5. Check this option to ensure all review threads must be resolved prior to merge.
  6. Click Save changes.

Once enabled, GitHub will automatically block merges until every conversation in the pull request has been marked as resolved.

Exceptions

  • This rule applies only to pull requests that have open review comments; it does not affect draft or unreviewed pull requests.
  • Admins can bypass this restriction unless “Include administrators” is also selected in the branch protection rule.
  • If a comment thread is reopened after being resolved, the pull request will again be blocked until it is closed.

Further Resources

Was this article helpful?

Powered by Product Fruits