update-nanoclaw

To sync upstream changes to a customized Git fork without losing local modifications, you can use a workflow that applies preflight checks, creates backup branches, and previews diffs before merging. This preserves your local drift while integrating upstream updates safely.

Previewing upstream Git commits before merging is handled by a diff-aware process that shows upstream changes versus local drift and lists potential conflicts. This allows you to review incoming updates and identify breaking changes before integration.

Rolling back a Git merge after a failed upstream sync uses a timestamped backup branch and tag created during preflight. This safety mechanism allows you to revert the working tree to its previous state if validation or tests fail.

You can choose between merge, cherry-pick, and rebase strategies when updating a fork. This flexibility lets you integrate upstream changes on your terms, selecting the specific Git workflow that best fits your deployment environment.

Breaking changes in a CHANGELOG affect Git upstream synchronization by triggering migration safety checks during the update process. The workflow detects these changes via changelog diffs and can trigger optional migrations to prevent environment failures.

Updating a customized Git fork requires a clean working tree and properly configured remotes to proceed safely. Preflight safety checks enforce these prerequisites before applying any upstream updates, backups, or rollback tags.