Apply the role suffix to every new repo, and audit before publish

Role suffix on every repo slug

Apply the role suffix to every new repo, and audit before publish

When creating any new repo under chirag127/oriz*, apply the role suffix from branding/repo-naming-suffixes.md: -site for websites, -ext for browser extensions, -vsc-ext for VS Code extensions, -cli for command-line tools, -worker for Cloudflare Workers, -fn for Firebase Cloud Functions, -data for canonical-store data repos. NPM packages are the only allowed suffix-free names because the @chirag127/ scope already disambiguates them. Audit before publish: every git push to a new repo URL must verify the repo slug ends in one of those suffixes, OR is a clean npm-package name (no suffix). A slug that doesn’t match is a naming mistake — rename via runbooks/workflow/rename-repo.md before the first push, not after, because GitHub repo redirects only fire after the rename and won’t retroactively rewrite a wrong name that was already cloned.

See also

• branding/repo-naming-suffixes.md — the full suffix table and migration plan
• runbooks/workflow/rename-repo.md — how to rename safely
• — the audit happens *before* the user-authorised push

Edit on GitHub · Back to index