DOS6037

Project default branch should not be 'master'

DOS6037

GitLab project Severitylow builtIn

Description

Projects should have migrated off the legacy master default branch to main (modern GitLab convention since 2021). Lingering master branches indicate either a pre-2021 project that hasn't been updated, or a fork from a legacy upstream — both warrant a migration plan. Less strict than GL_Project_DefaultBranch_Should_Be_Main (which also rejects develop, trunk, etc.).

Learn More

Recommendation

1. In a clone: git branch -m master main; git push -u origin main; git push origin --delete master. 
2. In GitLab: Settings > Repository > Default branch -> set to main. 
3. Update CI/CD references and protected branch rules.

Policy Rule

{
  "target": "GLProject",
  "if": {
    "allOf": [
      {
        "resource": "GLProject",
        "property": "DefaultBranch",
        "operator": "notEquals",
        "value": "master"
      }
    ]
  },
  "then": {
    "effect": "Audit"
  }
}
« DOS6036 DOS6038 »
Rule Details
  • Rule ID: DOS6037
  • Code: GL_Project_DefaultBranch_Should_Not_Be_Master
  • Platform: GitLab
  • Category: project
  • Severity: Severitylow
  • Type: builtIn
Related Rules

Copyright © DevOps Shield. All Rights Reserved. Privacy Policy | Cookie Policy | Terms and Conditions | v1.0.2