[WRONG BRANCH] chore(fork): Windows-first 維護骨架 - #1
Conversation
Keep the upstream ChatGPT account-pool product intact, isolate official npm/Pages and governance workflows to lidge-jun/opencodex, and add a local Windows gate for overlay docs and upstream review. Co-authored-by: Cursor <cursoragent@cursor.com>
|
✅ Deterministic PR hygiene checks passed. |
github-actions
Bot
changed the title
⏳ DRAFT
What to do
Its title has been prefixed with |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c66a9996b1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| throw new UpstreamCheckError(`unexpected git log line: ${JSON.stringify(line)}`); | ||
| } | ||
| const [sha, date, subject] = parts; | ||
| const files = runGit(["show", "--name-only", "--format=", sha], repoDir) |
There was a problem hiding this comment.
When upstream main receives a merge commit, git show --name-only --format= uses combined-merge semantics and can omit nearly every changed file. For example, the existing release merge ceed6bf5 reports only package.json here, while its first-parent diff contains 224 paths, so the generated review report materially understates the affected surface without even showing a … +N more warning. Use a first-parent diff such as git show --first-parent --name-only --format= <sha> (or an equivalent diff-tree invocation) for merge commits.
Useful? React with 👍 / 👎.
Bare gh pr create on a fork clone targets the parent repo. Record the SanHsien-only default and the single exception: explicit contribute-back consent in the current conversation. Co-authored-by: Cursor <cursoragent@cursor.com>
Cursor 的規則是 per-project 的，先前只有 opencodex 有這條，其餘 fork 都沒有。 內容與 AGENTS.md、Codex 的 ~/.codex/AGENTS.md、Antigravity 的 ~/.gemini/GEMINI.md 一致：gh 在 fork clone 的預設 repo 就是上游，所以每個 clone 先 gh repo set-default， 開 PR 明寫 --repo/--base/--head，建完讀輸出 URL 確認 owner；回貢上游要主人當次 對話明確同意。2026-08-22 一天內兩個工具各誤開一個上游 PR。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
documentation
README.md is the Traditional Chinese product page; README.en.md is English. GUI and docs-site retain only en and zh-TW. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
lidge-jun/opencodex.tools/dev_check.ps1), overlay docs, weekly upstream review, and CodeQL.Test plan
bun install --frozen-lockfilepwsh -NoProfile -File tools\dev_check.ps1(14 fork tests + link check)bun run typecheckbun tools/check-upstream-updates.ts(no new commits)ci.ymlon this PRbun run src/cli/index.ts startand open http://localhost:10100 to configure providers / account pool