authorgravatar for julius0216@outlook.comJulius Marminge <julius0216@outlook.com> 2026-10-11 17:36:20-07:00
committergravatar for noreply@github.comGitHub <noreply@github.com> 2026-10-11 17:36:20-07:00
log6ec6376e321cbc4ea202dee287497dac4582ea41
tree2f9c42ab68fb1815926ee3e79532e7fade7ff2a0
parent07993f39ff2741ca63804a4ff4c1641079aa4d88
signature Signed by PGP key B5690EEEBB952194

docs(mobile): point fork links to pingdotgg (#18433)

2 files changed, 2 insertions(+), 2 deletions(-)

apps/mobile/deps/README.md+1-1
...@@ -1,3 +1,3 @@...@@ -1,3 +1,3 @@
1The Enriched Markdown tarball comes from the [`fork/t3-mobile` branch](https://github.com/juliusmarminge/enriched-markdown/tree/fork/t3-mobile). Its `t3-fork.json` records the exact source commit and upstream base. File/skill link recognition, back navigation from horizontal blocks, table-image presses, and code-block headers use upstream implementations. The remaining fork adds clipboard metadata, parsed asset manifests, signed image source resolution, React media slots, and development-host autolinks.1The Enriched Markdown tarball comes from the [`fork/t3-mobile` branch](https://github.com/pingdotgg/enriched-markdown/tree/fork/t3-mobile). Its `t3-fork.json` records the exact source commit and upstream base. File/skill link recognition, back navigation from horizontal blocks, table-image presses, and code-block headers use upstream implementations. The remaining fork adds clipboard metadata, parsed asset manifests, signed image source resolution, React media slots, and development-host autolinks.
22
3To replace it, commit the fork changes, run `yarn install --immutable` and `yarn workspace react-native-enriched-markdown prepare` in the fork checkout, then `node scripts/pack-t3.mjs /path/to/t3code/apps/mobile/deps`. Bump the fork package version for each replacement, update the tarball path in `apps/mobile/package.json` and `pnpm-workspace.yaml`'s `allowBuilds`, and run `vp i` to update the lockfile. Native clients need rebuilding when this dependency changes.3To replace it, commit the fork changes, run `yarn install --immutable` and `yarn workspace react-native-enriched-markdown prepare` in the fork checkout, then `node scripts/pack-t3.mjs /path/to/t3code/apps/mobile/deps`. Bump the fork package version for each replacement, update the tarball path in `apps/mobile/package.json` and `pnpm-workspace.yaml`'s `allowBuilds`, and run `vp i` to update the lockfile. Native clients need rebuilding when this dependency changes.
docs/operations/mobile-screens-fork.md+1-1
...@@ -1,7 +1,7 @@...@@ -1,7 +1,7 @@
1# Building the mobile Screens dependency1# Building the mobile Screens dependency
22
3The mobile v5 stack uses a committed tarball from the3The mobile v5 stack uses a committed tarball from the
4[T3 Screens fork](https://github.com/juliusmarminge/react-native-screens/tree/t3-v5.0.0-t3.25).4[T3 Screens fork](https://github.com/pingdotgg/react-native-screens/tree/t3-v5.0.0-t3.25).
5The fork owns the integration changes; the app does not patch this package.5The fork owns the integration changes; the app does not patch this package.
6Each archive includes compiled JavaScript, declarations, native source and6Each archive includes compiled JavaScript, declarations, native source and
7`t3-fork.json` recording its version, source commit and upstream base.7`t3-fork.json` recording its version, source commit and upstream base.