SO-1279: add trust-engineering to CODEOWNERS - #223
Open
meeday wants to merge 1 commit into
Open
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 04f7732. Configure here.
meeday
enabled auto-merge (squash)
September 10, 2026 07:54
meeday
removed request for
a team,
andygriffiths-mv and
lewiscowles-netizen
September 10, 2026 07:54
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
1 participant
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.
Ownership reflection Wave 2 (https://linear.app/multiverse-io/issue/SO-1279). Adds the trust-engineering team as code owner alongside the legacy entry, per the confirmed ownership sheet. Legacy entries are removed in Phase 2 (SO-1283). Note: the trust-engineering team also needs a maintain grant on this repo for GitHub to accept it as a code owner; that grant is being applied separately by the org admin. No other files changed.
Note
Low Risk
Governance-only change to review assignment; no application or runtime behavior is affected.
Overview
Updates repo-wide CODEOWNERS so
@Multiverse-io/trust-engineeringis a co-owner alongside the existing@multiverse-io/xeniasentry for*, reflecting Wave 2 ownership without removing the legacy team yet.Reviewed by Cursor Bugbot for commit 04f7732. Bugbot is set up for automated code reviews on this repo. Configure here.