Skip to content

Configure dev branch protection and required CI gates #61

Description

@daniele21

dev is the canonical integration branch but is currently unprotected. The available GitHub connector does not expose branch-protection/ruleset writes, so this remains repository-administration work.

Configure dev so normal changes go through pull requests and cannot bypass the established product/repository gates.

Recommended required checks from the current workflows:

  • Repository health: adopted-contracts
  • Repository validation: validate (3.12), validate (3.13), Frontend (Node 24), Product E2E (Python 3.12)
  • Browser acceptance: Playwright (Chromium)
  • Built product: Build, smoke, package

Also disable force-push/deletion for dev unless there is a deliberate administrative exception. Keep release-only publication behavior separate from PR-required checks when the publish job is intentionally skipped on PRs.

Acceptance: dev reports protection/ruleset enforcement and a PR cannot merge while any required permanent gate above is failing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions