Repository navigation
chore: add engineering governance checks and ownership - #53
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the requested repository governance baseline: scoped code ownership, redacted Gitleaks scanning, a Conventional Commits check, Dependabot coverage and PR-template fields as needed.
New checks are not required status checks. Existing deployment workflows and runtime source are unchanged.
AI: Codex (model/version not exposed by this execution environment).
Validation: YAML parsed locally; changed paths restricted to governance configuration; action and Gitleaks revisions resolved against upstream; Gitleaks binary checksum pinned. GitHub CI and existing review requirements must pass before merge. CI results are not claimed until they are observed.
Private repositories blocked by Actions billing/quota remain open for the November 1 reset. No admin merge or protection bypass is authorized.