github-fork-sync-assistant

To sync GitHub forks with upstream in bulk, the process reads your forked repositories and performs per-repo upstream synchronization. It generates a status report for each repository, marking them as updated, current, or failed.

When syncing GitHub forks, archived repositories are automatically skipped. The tool detects archived repos, permission issues, or conflicts during the update process and bypasses them with a clear reason logged in the results.

Yes, you need the gh CLI installed and user authentication configured to synchronize forked repositories. The tool depends on gh CLI to access your GitHub account, verify repository permissions, and execute the upstream branch updates.

Yes, you can sync specific GitHub forks by providing a custom user-provided list. If you do not supply a specific list, the tool defaults to reading repository names from an assets file to perform the upstream synchronization.

Bulk fork synchronization handles merge conflicts by skipping the affected repository. When a conflict, permission error, or archived status is encountered, the update is aborted for that specific repo and marked as a sync failure in the results.