self-update

To update pkdx without losing data, the self-update skill automates safe stash, pull, and merge operations while preserving your local configurations. It guides you through conflict resolution to ensure customizations remain intact during the version control process.

The safest git workflow for migrating a forked pkdx repository involves syncing changes from upstream while protecting local data. The process uses stash operations and user-guided conflict resolution to merge updates without overwriting customizations.

To resolve merge conflicts when pulling upstream changes, the update process halts and provides user-guided resolution for conflicting files. This ensures you manually verify and retain necessary local modifications before completing the git merge.

Yes, you can run binary updates and data migrations simultaneously. The update process fetches or builds the latest binaries and then executes metadata migrations to ensure your local installation stays fully synchronized with the upstream repository.

The pkdx update process works with both direct clones and forked repositories. It provides specific guidance for syncing local changes in fork-based workflows and handles standard upstream pulls for direct clone installations.

During an automated version control update, you must manually handle merge conflicts when local customizations collide with upstream changes. The process pauses to require user-guided resolution for conflicting files before it can safely resume the migration.