Skip to content

docs(agents): drop obsolete fork stack workflow - #410

Merged
patroza merged 5 commits into
fork/devfrom
docs/cleanup-agents-md
Aug 15, 2026
Merged

docs(agents): drop obsolete fork stack workflow#410
patroza merged 5 commits into
fork/devfrom
docs/cleanup-agents-md

Conversation

@omegent-app

@omegent-app omegent-app Bot commented Aug 15, 2026

Copy link
Copy Markdown

AGENTS.md is the single current fork workflow:

  • change PRs target fork/dev and squash-merge
  • update main from upstream/main, then classic-merge into fork/dev
  • catching a change PR up is rebase or merge — pick one

Removed the historical stack/handover docs (docs/fork-stack.md, docs/fork-base.md, docs/stable-dev-release-branch-handover.md) so they cannot describe a past or future model.

Grok 4.6 / T3 Discord

opened by patroza in chat thread Discord · Discord · T3

AGENTS.md still described overlays, pr-stack.json, and the old
fork/base → tim → candidates → changes → integration restack.
The only live model is PRs against fork/dev (squash-merge),
fast-forwarding main from upstream then classic-merging into
fork/dev, and catching change PRs up by rebase or merge.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
@omegent-app
omegent-app Bot marked this pull request as ready for review August 15, 2026 14:19
omegent-app Bot and others added 2 commits August 15, 2026 14:20
AGENTS.md is the single description: PRs target fork/dev and
squash-merge, main fast-forwards from upstream then classic-merges
into fork/dev, and catching a PR up is rebase or merge.

Delete the historical stack/handover docs so they cannot contradict
that, and point the remaining CI note at fork/dev.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Draft PRs do not need a rebase or merge of latest fork/dev.
That step is for published PRs that are behind or conflicting.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Draft and no-PR pushes run vp check only on files changed against
fork/dev. Publishing requires HEAD to contain latest fork/dev, then
the full ship gate. After a PR is ready, stay on it until required
checks are green.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 15, 2026
## Summary

The thread PR panel used the project's primary repository identity. On a
fork that prefers **upstream**, so `#410` was loaded as
`pingdotgg#410`.

That number exists only on the fork:

| Repo | #410 |
| --- | --- |
| `patroza/t3code` | open — docs(agents): drop obsolete fork stack
workflow |
| `pingdotgg/t3code` | GraphQL: could not resolve |

The agent on the left found the fork PR (`gh pr view 410` with `GH_REPO`
/ origin). The panel asked GitHub for the upstream number and showed
**Pull request not found**.

This is not the earlier App-install / wrapper issue. Ops #81 and product
#408 already landed; t3vm is minting public-read fallback tokens.

**Fix:** open the panel from the change-request URL (`patroza/t3code`),
and accept any of the checkout's remotes on the server so origin is
still this project.

## Test plan

- [x] `vp test run
apps/server/src/pullRequest/PullRequestService.test.ts
apps/web/src/components/pullRequest/pullRequestDetail.logic.test.ts`
- [ ] After deploy: open the `#410` thread panel and confirm it loads
`#410`
- [ ] Confirm an upstream PR on the same checkout still opens against
`pingdotgg/t3code`

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
Changed-file vp check is only for fmt/lint of the diff. Workspace
vpr typecheck still runs on every draft and no-PR agent push.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
@patroza
patroza merged commit ab26845 into fork/dev Aug 15, 2026
6 checks passed
omegent-app Bot added a commit that referenced this pull request Aug 15, 2026
…ge-guard

#410 dropped the obsolete fork stack workflow section this branch had edited.
Kept its simplification and folded the sync-merge rule into the existing
"Updating from upstream" bullet instead of resurrecting the old section.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant