forgejo mirror of agentic-os and agentic-os-kai main has diverged from github #5

New issue

Closed

opened 2026-05-23 20:54:25 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:54:25 +00:00

Owner

Originally filed by @coilysiren on 2026-05-22T20:43:45Z - https://github.com/coilysiren/infrastructure/issues/287

The origin remote for agentic-os and agentic-os-kai has one fetch URL (github) and two push URLs (github + forgejo.coilysiren.me). Every git push therefore targets both.

The forgejo mirror's main has diverged from github's main for both repos. Pushes now land on github and get rejected non-fast-forward on forgejo. Likely cause: release-please force-pushes github main, the forgejo side never receives the rewrite, and the two histories drift apart permanently.

Pick one: make forgejo a pull mirror of github (not a push target), or reconcile the two histories once and keep forgejo fast-forward-only. Today every push to these two repos half-fails.

_Originally filed by @coilysiren on 2026-05-22T20:43:45Z - [https://github.com/coilysiren/infrastructure/issues/287](https://github.com/coilysiren/infrastructure/issues/287)_ The `origin` remote for `agentic-os` and `agentic-os-kai` has one fetch URL (github) and two push URLs (github + `forgejo.coilysiren.me`). Every `git push` therefore targets both. The forgejo mirror's `main` has diverged from github's `main` for both repos. Pushes now land on github and get rejected non-fast-forward on forgejo. Likely cause: release-please force-pushes github `main`, the forgejo side never receives the rewrite, and the two histories drift apart permanently. Pick one: make forgejo a pull mirror of github (not a push target), or reconcile the two histories once and keep forgejo fast-forward-only. Today every push to these two repos half-fails.

coilysiren referenced this issue

2026-05-23 20:54:40 +00:00

tailscale loopback: kai-server host userspace cannot reach its own ts-proxy at 100.115.195.2:8428 #89

coilysiren added the

label

2026-06-04 08:16:57 +00:00

coilysiren commented

2026-06-17 08:23:02 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:02 +00:00