chore(hygiene): normalize Forgejo endpoint and fj usage #2

Merged
troed merged 1 commit from chore/hygiene-forgejo-endpoint into main 2026-08-26 21:25:26 +02:00
Owner

Follow-up to hygiene #1: unify Forgejo endpoint handling.

  • AGENTS.md: add Repo & Forgejo section with canonical fj -H git.sync.wtf pattern (api host vs ssh://git@<forgejo-ssh-host>:2221 remote) matching starfleet/computer, roster, and now communicator-esp32
  • Previously no Forgejo guidance; now identical lesson across starfleet
  • Local remotes unified to ssh://git@192.168.0.2:2221/... (was headless.local for sailfish, 192.168.0.2 for esp32/computer) so Always pass -H git.sync.wtf applies uniformly

Verification: fj -H git.sync.wtf pr search works from both repos; hygiene scan clean (192.168 only in generic 192.168.1.10 doc example and vendor).

Follow-up to hygiene #1: unify Forgejo endpoint handling. - AGENTS.md: add Repo & Forgejo section with canonical `fj -H git.sync.wtf` pattern (api host vs `ssh://git@<forgejo-ssh-host>:2221` remote) matching `starfleet/computer`, `roster`, and now `communicator-esp32` - Previously no Forgejo guidance; now identical lesson across starfleet - Local remotes unified to `ssh://git@192.168.0.2:2221/...` (was `headless.local` for sailfish, `192.168.0.2` for esp32/computer) so `Always pass -H git.sync.wtf` applies uniformly Verification: `fj -H git.sync.wtf pr search` works from both repos; hygiene scan clean (`192.168` only in generic 192.168.1.10 doc example and vendor).
- AGENTS.md: add Repo & Forgejo section with canonical fj -H
  git.sync.wtf pattern (api host vs ssh://git@<forgejo-ssh-host>:2221)
  matching computer/esp32/roster. Previously no Forgejo guidance,
  now identical lesson across starfleet.
- Unify local remotes to ssh://git@192.168.0.2:2221/... (was
  headless.local for sailfish, 192.168.0.2 for esp32/computer)
  so 'Always pass -H git.sync.wtf' applies uniformly.
troed merged commit 29461915cc into main 2026-08-26 21:25:26 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
starfleet/communicator-sailfish!2
No description provided.