← knowledge.oriz.in

chirag127 owns everything — oriz-org dissolved 2026-07-02

decision orggithubbrandingrecruitermigration

chirag127 owns everything — oriz-org dissolved

Decision

All GitHub repos live at chirag127/<name>. The oriz-org GitHub org is dissolved after all transfers complete.

Layout

Repo class Location Example
Own chirag127/* chirag127/oriz-blog, chirag127/constants-api
Forks chirag127/* chirag127/OmniRoute (upstream = diegosouzapw/OmniRoute)
Umbrella chirag127/workspace Formerly oriz-org/workspace; renamed 2026-07-02
Reusable workflows chirag127/oriz-workflows New — canonical GH Actions workflows for the whole fleet
Shared packages chirag127/oriz-<name> published to npm as @oriz/* e.g. @oriz/astro-integration

Why (2026-07-02)

Reversing the keep-oriz-org-recruiter-via-pinning strategy. New reasons override:

  1. Consistency after fork migration. Forks moved to chirag127 on 2026-07-01 (see fork-thin-upstream-tracking) because org-owned forks broke maintainer_can_modify on upstream PRs. Split ownership creates ongoing confusion.
  2. Recruiter view unchanged. GitHub renders cross-org contributions on chirag127 profile via the contribution graph. Pinning worked; direct ownership works better — repo count + star count appear on-profile.
  3. PR authorship. External PRs to chirag127/repo present as personal-project contributions. oriz-org/repo PRs read as semi-corporate; some maintainers treat them differently.
  4. Simpler mental model. One namespace, one place for issues, one profile URL to share.
  5. Secrets consolidation. Org-level secrets replaced by umbrella-owned secrets model — see workspace-owns-secrets-2026-07-02.

What "oriz" as brand becomes

Migration mechanics

Use gh repo transfer <src> <dst-owner>:

Cross-refs