zeekay
fea2a2612f
Complete rebrand. Code now reads as a first-party Hanzo project, not
a forked codebase with upstream identifiers leaking through.
tsconfig path aliases (9 entries):
@gitroom/backend → @social/backend
@gitroom/frontend → @social/frontend
@gitroom/helpers → @social/helpers
@gitroom/nestjs-libraries → @social/nestjs-libraries
@gitroom/react → @social/react
@gitroom/plugins → @social/plugins
@gitroom/orchestrator → @social/orchestrator
@gitroom/extension → @social/extension
Workspace package names (apps/*/package.json):
postiz-backend → social-backend
postiz-frontend → social-frontend
postiz-orchestrator → social-orchestrator
postiz-extension → social-extension
postiz-command → social-command
@postiz/node → @social/node
Swept across 477 files: every import statement, env var (POSTIZ_*→SOCIAL_*),
identifier (featured_by_gitroom→featured_by_social, FEATURED_BY_GITROOM enum
key→FEATURED_BY_SOCIAL), prose mention, FAQ string, and i18n value in all
23 locale JSONs.
Preserved (required by AGPL-3.0): upstream-fork attribution in SECURITY.md,
README.md, CLAUDE.md ("hard fork of gitroomhq/postiz-app"). Required for
license compliance; not used by any code path.
Preserved (external npm dep): @postiz/wallets — this is a published wallet
provider package, not workspace code. We pull it as a normal dependency.
Verification: `grep -riE "postiz|gitroom" --include={ts,tsx,json,mjs,js,md,yaml,yml}`
excluding node_modules + legal docs + i18n.lock returns 0.
1.2 KiB
1.2 KiB
What kind of change does this PR introduce?
eg: Bug fix, feature, docs update, ...
Why was this change needed?
Please link to related issues when possible, and explain WHY you changed things, not WHAT you changed.
Other information:
eg: Did you discuss this change with anybody before working on it (not required, but can be a good idea for bigger changes). Any plans for the future, etc?
Checklist:
Put a "X" in the boxes below to indicate you have followed the checklist;
- I have read the CONTRIBUTING guide.
- I have signed the Contributor License Agreement (CLA) (ICLA for individuals, CCLA for entities).
- I confirm I have not used AI to submit this PR or generate code for it.
- I checked that there were no similar issues or PRs already open for this.
- This PR fixes just ONE issue