docs: align agent instructions with upstream - #92
Conversation
github-actions
Bot
added
size:S
vouch:trusted
![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: 97cb3b4a69
ℹ️ 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".
| - Keep fork-only storage in `state-tarik02.sqlite` unless intentionally upstreaming it. | ||
| - When preparing fork PRs, branch from `origin/main` and target `tarik02/t3code:main`. | ||
| - If a fork PR branch accidentally includes upstream history, rebuild it from `origin/main` and replay only the intended diff. | ||
| Fork-specific behavior and maintenance notes are documented in `FORK.md`. |
There was a problem hiding this comment.
When an agent makes a fork-only change, this pointer is not an equivalent replacement for the removed instructions: FORK.md inventories current behavior but does not tell the agent to update that inventory, base fork PRs on origin/main, target tarik02/t3code:main, or repair branches containing upstream history. Those workflows therefore lose their only repository-specific safeguards; migrate the still-applicable procedural rules into FORK.md before replacing them with this pointer.
AGENTS.md reference: AGENTS.md:L7-L7
Useful? React with 👍 / 👎.
1 participant
What Changed
AGENTS.mdnow matches upstream except for one sentence directing maintainers toFORK.mdfor fork-specific behavior and maintenance notes.Why
Keeping fork rules in
FORK.mdavoids instruction drift and reduces conflicts during upstream syncs while preserving discoverability.Checklist