Skip to content

chore: update .github/CODEOWNERS — current entries point to non-Safrochain handles #36

Description

@danbaruka

Summary

The current .github/CODEOWNERS file lists handles that do not appear to be Safrochain organization members:

```

This looks like a leftover from an upstream fork. As a result, every PR opened against this repo automatically requests reviews from people outside the org, which is noisy for them and means Safrochain maintainers are not auto-requested.

Why this matters

  • PR review requests should reach the Safrochain maintainers responsible for each area
  • External handles getting auto-requested on every PR is poor etiquette and may eventually have them block notifications
  • CODEOWNERS is also the foundation for branch protection rules that require code-owner approval

Proposed change

Replace the wildcard line with rules that reflect the actual Safrochain team. A reasonable starting layout:

```

Default owners for everything

  •                   @Safrochain-Org/maintainers
    

Custom modules

/x/clock/ @Safrochain-Org/core
/x/cw-hooks/ @Safrochain-Org/core
/x/drip/ @Safrochain-Org/core
/x/feepay/ @Safrochain-Org/core
/x/feeshare/ @Safrochain-Org/core
/x/globalfee/ @Safrochain-Org/core
/x/tokenfactory/ @Safrochain-Org/core
/x/wrappers/ @Safrochain-Org/core

App wiring and consensus

/app/ @Safrochain-Org/core

Build / CI / release

/.github/ @Safrochain-Org/devops
/Makefile @Safrochain-Org/devops
/Dockerfile @Safrochain-Org/devops
/goreleaser.yml @Safrochain-Org/devops

Docs

/docs/ @Safrochain-Org/docs
/README.md @Safrochain-Org/docs
```

(Replace team slugs with the actual GitHub teams that exist under the Safrochain-Org org, or use individual handles if no teams are defined yet.)

Acceptance criteria

  • No GitHub handles outside the Safrochain-Org org remain in CODEOWNERS
  • Path-specific rules cover at least /x/, /app/, /.github/, and /docs/
  • A test PR confirms the correct owners are auto-requested

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationhelp wantedExtra attention is needed

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions