Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,003
    • Issues 52,003
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,574
    • Merge requests 1,574
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #328462
Closed (promoted) (promoted)
Open
Issue created Apr 20, 2021 by Austin Regnery@aregnery🔴Developer

Framework for source code rules

Opportunity to investigate

GitLab offers a number of controls that can be implemented as safeguards. These controls can be put in place to keep changes from having a negative or enforce adherence to policies. Integrating features like protected branches, approval rules, code owners (approvals) and soon “status checks” should have an experience that easy to set up, maintain, and consume downstream.

Research insights

  • Video walk through of the CM Scorecard Recommendations - Create:Source Code:Code Review FY21-Q2 (see video description for chapter markers and references)
  • Issues related to CM Scorecard Recommendations - Create:Source Code:Code Review FY21-Q2
    • Specific issue: Improve the organization of repository and merge request policy settings. Explanation of the severity of the issue: #258577 (comment 450874492)

Feature comparison

Figma 👉 https://www.figma.com/file/NKRTU2J6fsprk0dHq20NVy/Integrate-the-experience-for-safeguards?node-id=2%3A0

Comparison

🤝 Cross-stage Collaboration

cc groupcode review Kai, Pedro

cc groupcompliance Sam, Austin

Edited Jun 22, 2021 by Mike Nichols
Assignee
Assign to
Time tracking