5d4309314d
All checks were successful
sync-to-forgejo / sync (push) Successful in 15s
GitHub->Forgejo sync (sync-to-forgejo.yml) had been failing since 2026-07-10 because it used a rebase-then-push strategy that assumed Forgejo was always a fast-forward mirror of GitHub. FluxCD's own ImageUpdateAutomation commits directly to Forgejo (the repo Flux's GitRepository actually watches), so Forgejo had accumulated ~70 automated image-bump commits GitHub never saw, which made the rebase fail. Meanwhile GitHub had a handful of manually/CI-pushed gitops deploy commits Forgejo never received. This merge reconciles both histories without discarding either side; both remotes fast-forward to this commit. # Conflicts: # apps/nxtgauge-admin-solid/overlays/prod/release-patch.yaml # apps/nxtgauge-frontend-solid/overlays/prod/release-patch.yaml |
||
|---|---|---|
| .. | ||
| ai-guard | ||
| forgejo | ||
| github-actions-runners/base | ||
| litellm | ||
| nxtgauge-admin-solid | ||
| nxtgauge-ai-assistant | ||
| nxtgauge-backend-rust | ||
| nxtgauge-frontend-solid | ||
| ollama/base | ||
| postgresql | ||
| registry | ||
| traceworks2026 | ||