chore: point repo references at the plainlang org (ENG-194) - #21
Merged
Conversation
The GitHub organization moved from Codeplain-ai to plainlang, so every hardcoded `Codeplain-ai/plain-forge` string is now stale. - package.json: repository.url, homepage, bugs.url — these ship inside the published tarball and drive the npm page's Repository link. - bin/cli.mjs: the usage-guide link printed after install. - scripts/deploy.sh: REPO, used by the workstation-publish path for the release lookup and the Deployments API call. - RELEASING.md: the changelog-link template and the trusted-publisher row. .github/workflows/publish.yml needs no change: it never hardcodes the org, reaching for github.repository and github.server_url instead, and auth is OIDC. The npm trusted-publisher entry has already been repointed. The RELEASING.md link to Codeplain-ai/codeplain is left as-is — that repo has not moved.
zanjonke
changed the title
VitjanZ
approved these changes
Aug 28, 2026
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
2 participants
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.
The GitHub organization moved from
Codeplain-aitoplainlang, leaving every hardcodedCodeplain-ai/plain-forgestring stale. This repoints all five occurrences.Changed
package.json—repository.url,homepage,bugs.url. These matter most: they are baked into the published tarball and drive the npm page's "Repository" link.bin/cli.mjs— the usage-guide link printed after install.scripts/deploy.sh—REPO, used by the workstation-publish path for the release lookup and the Deployments API call.RELEASING.md— the changelog-link template and the trusted-publisher row.Deliberately unchanged
.github/workflows/publish.ymlneeds no change. It never hardcodes the org — it reaches for${{ github.repository }}and${{ github.server_url }}for the Slack run-log links, and auth is OIDC with no repo string in the workflow. The only org-coupled piece is the npm trusted-publisher entry, which has already been repointed on npmjs.com. Same story forci.ymlandpr-notify.yml.RELEASING.md:17links toCodeplain-ai/codeplain. That repo has not moved — the API still reportsfull_name: Codeplain-ai/codeplain, andplainlang/codeplain404s. Leave it until that repo moves too.Worth confirming outside this PR
Neither is visible from the working tree, and an inter-org transfer can drop them:
SLACK_WEBHOOK_URLrepo secret and thenpmenvironment (Settings → Environments / Secrets).main, including the requiredTest (node 18 / 20 / 22)check.Testing
npm test— 58/58 passing.