eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Note upstream history rewrite as a spork sync failure mode

Browse source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-03-29 08:22:11 -07:00
commit 99df78664e
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/how-to/configuration/manage-spork-branches.md
View file

@ -98,7 +98,7 @@ git push --force-with-lease origin feature/upstream/my-change
The next mirror-sync run will pick up the resolved branch and rebuild `deploy`. The next mirror-sync run will pick up the resolved branch and rebuild `deploy`.
**TODO:** Rebase failures are currently only visible in the Forgejo Actions UI. Alerting via Grafana is planned but not yet implemented. **TODO:** Workflow failures — whether from rebase conflicts or upstream history rewrites (force-push on main) — are currently only visible in the Forgejo Actions UI. Alerting via Grafana is planned but not yet implemented.
## Future: `.spork.toml` ## Future: `.spork.toml`