Skip to content

chore: remove CODEOWNERS entries now enforced org-wide (ENG-2013) - #12497

Open
hamishfagg wants to merge 1 commit into
stagingfrom
hamish/eng-2013-remove-codeowners
Open

chore: remove CODEOWNERS entries now enforced org-wide (ENG-2013)#12497
hamishfagg wants to merge 1 commit into
stagingfrom
hamish/eng-2013-remove-codeowners

Conversation

@hamishfagg

@hamishfagg hamishfagg commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

What

Deletes .github/CODEOWNERS. The org-level ruleset in mindsdb/terraform (newprod/global/github) requires a @mindsdb/devops review on the paths common to all repos, and enforces each repo's CODEOWNERS through require_code_owner_review. So: shared paths leave this file, repo-specific ones stay.

Removed:

/.github/workflows/ @mindsdb/devops

Why

One org-wide policy in terraform for what every repo shares; CODEOWNERS for what only this repo needs. Neither duplicates the other.

Targets staging so it reaches main with the next release.

🤖 Generated with Claude Code

Paths every repo shares (.github/, Dockerfile, Makefile, docker/, alembic/,
pyproject.toml, ...) now require a @mindsdb/devops review through the org-level
ruleset in mindsdb/terraform, so they leave this file. Anything specific to this
repo stays here; the same ruleset enforces CODEOWNERS via
require_code_owner_review.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@hamishfagg
hamishfagg force-pushed the hamish/eng-2013-remove-codeowners branch from 80f4e13 to 3a347a0 Compare September 10, 2026 05:08
@hamishfagg hamishfagg changed the title chore: remove CODEOWNERS, now enforced by the org ruleset (ENG-2013) chore: remove CODEOWNERS entries now enforced org-wide (ENG-2013) Sep 10, 2026

@lucas-koontz lucas-koontz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi: Reviewed the CODEOWNERS deletion and the organization ruleset. Shared workflow ownership remains required on main. This PR targets staging, where the baseline does not apply and review requirements are already disabled. Automatic DevOps review requests on staging cease when this merges; main changes on promotion.

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.

2 participants