repo-sync-updater

To sync a local repository with upstream, you run a script on your backend host that enforces fast-forward pulls, validates prerequisites like npm ci, and refreshes Playwright chromium installations to ensure runtime readiness for tracker tasks.

Yes, you can preview git sync changes before applying them using the dry-run mode, which allows you to inspect upstream updates and avoid unintended mutations to your local repository working tree.

If your git working tree is dirty before a repository sync, the process detects the uncommitted changes and halts, but you can use the optional dirty-state bypass with the allow-dirty flag to proceed.

Yes, this repository sync workflow explicitly supports WSL or similar hosts to perform safe git operations, validate prerequisites, and refresh the backend stack for production-grade automation tasks.

You need to restart the backend service after pulling upstream repository updates because runtime dependencies and configurations may have changed, requiring a service restart to ensure a reliable, healthy synchronization state for tracker jobs.

The best way to prevent tracker job failures from outdated backend dependencies is to automatically refresh prerequisites like running npm ci and installing Playwright chromium immediately after synchronizing your local clone with the upstream branch.