Skip to content

chore: enforce CI strictness on protected branches #23

@Brad-Edwards

Description

@Brad-Edwards

Mirror the moonbase CI-strictness baseline (where it applies to this repo):

  • Branch protection on main (+ dev if used); changes land via PR.
  • All CI checks required to merge, strict; admins may bypass.
  • SonarCloud: sonar.qualitygate.wait=true + a gate that fails on any new issue.
  • pre-commit (file hygiene + secret scan) wired and enforced in CI.

Goal: nothing merges past failing checks or a failing quality gate; admin override retained.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions