Skip to content

[T-132] Configure branch protection, merge settings and project board for main #31

Closed

Description

@CodewithJha

Task T-132 · Milestone M1 — Foundation · Size XS · Priority P2 · Epic #1

Branch chore/t-132-configure-branch-protection-merge-settings — one task = one branch = one PR (doc 32 §6)

Summary

Apply the repository settings of doc 20 §3 and doc 32 §1/§6: protected main with required checks, linear history, squash-only merges, delete-branch-on-merge, conversation resolution, and a free GitHub Project board for the backlog.

Context / motivation

Trunk-based development with green CI only works if the platform enforces it. This is a repo-settings task (owner action), documented so it is reproducible.

Scope

In scope

  • Branch protection/ruleset on main: required checks from doc 20 §3, linear history, no force-push, conversation resolution.
  • Repo settings: squash merge only, PR title as commit message, auto-delete head branches.
  • GitHub Project (board) with columns Backlog / Ready / In progress / In review / Done mirroring doc 32 §1, auto-adding issues labelled task.
  • Document the settings in docs/20 §3 (as-built).

Implementation guidance

  • Can be done via gh api (rulesets endpoint) or UI; record the exact commands/settings in the PR description so they can be re-applied.
  • Standards: respect the layering contracts (doc 16 §2) and conventions in doc 34; no hard-coded tunables — thresholds/defaults come from typed settings (doc 27); no magic numbers (ruff PLR2004); public APIs typed (mypy strict) and documented.

Acceptance criteria

  • Direct pushes to main rejected; PR without green required checks cannot merge.
  • Project board exists and lists open task issues.
  • Doc 20 §3 reflects the configured state.
  • Tests listed below added and green in CI; coverage of new code meets the gate in doc 18 §3.
  • Docs, config reference and CHANGELOG Unreleased updated where behaviour, keys or interfaces changed.
  • Definition of Done (doc 32 §3) satisfied.

Tests required

  • Unit tests for all new behaviour.

Dependencies

Blocked by: #28 (T-006a)

Blocks: no other task (leaf)

Parallelization notes

Files / paths owned by this task — avoid editing other paths; shared files (pyproject.toml entry points, cli/main.py, api/routers/__init__.py, router.tsx, docker/compose.yaml, ci.yml) are append-only:

  • docs/20-ci-cd-and-devops.md (§3 as-built note)

Settings only; no code conflicts.

Definition of Done

Per doc 32 §3 and AGENTS.md §5: lint, format, mypy strict and import-linter green; tests added and passing; docs updated; PR template completed with Closes #<this issue>; Conventional Commit messages referencing T-132 (doc 16 §6); commits authored only by the repository owner identity (AGENTS.md §4); CI green; reviewer checklist (doc 32 §5.1) satisfied.

References

Design docs: doc 20 §3 · doc 32 §1 · doc 32 §6 · doc 16 §6

External:

Activity

  1. added this to the M1 — Foundation milestone on Nov 19, 2026
  2. added
    type:choreMaintenance / scaffolding
    area:ciCI/CD workflows
    priority:P2Important, not blocking
    taskChild task of a milestone epic
    on Nov 19, 2026
  3. CodewithJha commented on Nov 19, 2026

    @CodewithJha
    OwnerAuthor

    Skipped by the autonomous backlog run (worker B) and marked status:needs-owner. This task changes repository admin settings: a ruleset with required checks and conversation resolution, plus merge settings. It also creates a GitHub Project, which needs the project token scope. Turning on required checks and conversation resolution while parallel PRs are in flight would block in-progress merges. It should be applied by the owner once the backlog run is paused. The PR description template from the issue (exact gh api commands) still applies.

  4. moved this to In progress in RoboProbe backlogon Nov 19, 2026
  5. added a commit that references this issue on Nov 19, 2026
    63f6a41
  6. CodewithJha commented on Nov 19, 2026

    @CodewithJha
    OwnerAuthor

    Merged via #253. One owner-only UI step remains: enable the project's Auto-add to project workflow for label:task (doc 20 §3.1).

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

    area:ciCI/CD workflowsmilestone:M1M1 — Foundationpriority:P2Important, not blockingsize:XS< 2 hourstaskChild task of a milestone epictype:choreMaintenance / scaffolding

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions