CI and Automation

CI and automation policy ensures local workflows and hosted pipelines evaluate the same gates with predictable outcomes.

Visual Summary

flowchart TD
    local[local gate execution] --> pr[pr workflows]
    pr --> required[required status checks]
    required --> release[release workflow triggers]

Automation Scope

• build, test, and contract workflows
• docs build and publish workflows
• release workflows for crate and package publication
• guardrail workflows for repository layout and ownership rules

Alignment Rules

• local make targets must mirror CI gate composition
• path filters must reflect real ownership boundaries
• failure messages must name owning surface and remediation path

Pipeline Ownership Rule

Every required workflow must declare:

• owning maintainer role
• owning handbook page for remediation guidance
• escalation path when the owner is unavailable

Code Anchors

• .github/workflows/
• makes/gh.mk
• crates/bijux-dev/src/suites/repo.rs

Next Reads

• Repository Gates
• Release Operations
• Change Control