update-nanoclaw

To safely sync upstream changes into a customized git fork, you need a process that enforces a clean working tree, creates backup branches, and validates updates. This approach preserves local modifications while reliably applying upstream changes.

The best way to pull upstream changes without losing local modifications is to use rollback safeguards like backup branches and tags before merging. This ensures you can preview upstream changes and revert if breaking changes are detected.

Yes, you can preview upstream git changes before merging them into your fork. A safe synchronization process allows you to compare upstream updates against your local repository to identify breaking changes before committing.

To cherry-pick specific upstream commits while keeping your fork clean, enforce a clean working tree first, then apply the cherry-picks with validation checks. This selective update method preserves local customizations without a full merge.

A rollback-safe git rebase works by creating backup tags and branches before rewriting commit history with upstream updates. If the rebase introduces breaking changes or conflicts, you can immediately restore your previous working state.

You need a clean working tree before merging upstream changes to prevent merge conflicts and data loss. Enforcing a clean state ensures backup creation and update validation can proceed reliably without overwriting uncommitted local modifications.