Skip to content

Enforce CI and review gates for money-path changes#114

Merged
Augustas11 merged 1 commit into
mainfrom
ci/enforce-money-path-gates
Jun 22, 2026
Merged

Enforce CI and review gates for money-path changes#114
Augustas11 merged 1 commit into
mainfrom
ci/enforce-money-path-gates

Conversation

@Augustas11

Copy link
Copy Markdown
Owner

Summary

  • Add .github/CODEOWNERS entries for money/auth paths and CI gate controls.
  • Add a stable ci-required aggregate job that fails unless coordinator Go, gateway Go, integration, deploy-tooling, SPEC-014, and Swift test jobs all pass.
  • Created GitHub ruleset 17964007 on main requiring PRs, code-owner review, resolved threads, stale-review dismissal, strict up-to-date checks, and ci-required.

Validation

  • ruby YAML parse for .github/workflows/ci.yml
  • git diff --check
  • GitHub ruleset readback confirms pull_request and required_status_checks requiring ci-required

Notes

  • Existing untracked specs/ files in the worktree were left untouched.
  • The branch CI run is expected to produce the new ci-required context for the ruleset.

Add a stable aggregate CI check for branch protection and CODEOWNERS coverage for the money/auth paths plus CI-control files.

Constraint: DEVE-1 is already partly fixed by CI jobs, so the remaining gap is merge enforcement.

Rejected: Path-limited duplicate workflow | existing CI already runs the Go, Swift, and integration suites on every PR.

Confidence: high

Scope-risk: narrow

Directive: Keep ci-required stable if branch protection depends on it; add jobs behind the aggregate rather than renaming the required context.

Tested: ruby YAML parse for .github/workflows/ci.yml; git diff --check; GitHub ruleset 17964007 readback shows pull_request and required_status_checks requiring ci-required.

Not-tested: Remote GitHub Actions run for this branch has not completed yet.
@Augustas11 Augustas11 merged commit 1d50dab into main Jun 22, 2026
7 checks passed
@Augustas11 Augustas11 deleted the ci/enforce-money-path-gates branch June 22, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant