Skip to content

chore: verify and configure branch protection rules for main and dev #2

@digital-michael

Description

@digital-michael

Goal

Ensure main and dev are protected against direct pushes and force-pushes before any code work begins.

Acceptance criteria

  • main: require PR + 1 approval, require status checks to pass, no direct push, no force push
  • dev: require PR, require status checks to pass, no direct push, no force push
  • Confirmed in repo Settings → Branches

Notes

Branch protection was previously set up on main during initial setup. Verify the full ruleset is correct and extend it to dev.

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase:0Phase 0 — Fork, rename, CI, toolingtype:choreMaintenance, tooling, CI, build

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions