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 linear history is enforced on the default branch

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

Why this matters

A linear commit history prevents merge commits on protected branches. It keeps history easy to follow and simplifies revert and forensic analysis. GitHub enforces this through the Require linear history branch protection setting, which forces squash or rebase merges into the protected branch. 

What this check does

This check verifies that the default branch is covered by a branch protection rule with Require linear history enabled. GitHub requires that squash or rebase merging be allowed in the repository before you can enable this setting.

How to fix it

From the GitHub web console

Open the repository.

  1. Go to Settings → Branches.
  2. Under Branch protection rules, click Add rule or edit the rule for the default branch (for example, main).
  3. Enable Require linear history.
  4. Save the rule. GitHub Docs+1

Note: Squash merge or rebase merge must be allowed in the repository to enable linear history. 

Exceptions

  • The rule applies only to branches targeted by the protection rule.
  • Admins can bypass protections unless you also enforce protections for administrators.

Further Resources

Was this article helpful?

Powered by Product Fruits