On 2026-09-15, ghorgsync v0.6.0 was released for the CLI that clones and keeps a local directory in sync with a GitHub organization or user account. This release focuses on speed and control for users managing many repositories. The headline improvement is parallel repository processing, allowing sync operations to use multiple workers and complete faster on multi-core machines while remaining non-destructive and safe.

What’s new

Parallel repository processing is now built in. ghorgsync v0.6.0 processes repositories concurrently instead of strictly one at a time.

  • A new --workers N flag sets the maximum number of repositories processed concurrently. The same setting can be provided via the GHORGSYNC_WORKERS environment variable.
  • Precedence is clear: an explicit flag overrides the environment variable, which overrides the default.
  • The default is 4 times the number of logical CPUs reported by the system at startup. The effective worker count is printed at startup so you can confirm the setting.
  • --clean mode always runs with a single worker to preserve interactive prompts.
  • Output is mutex-guarded to keep progress messages readable when running in parallel, and verbose mode now reports discovery time, scan time, per-repository processing time, and total elapsed time.

Documentation in README and USAGE.md has been updated with a Repository Concurrency section and examples.

No breaking changes were introduced. Existing workflows continue unchanged, and users who prefer strict sequential processing can force it with --workers 1.

Why it matters

For individuals and teams mirroring large organizations, sync time is often dominated by waiting on many repositories to clone, fetch, and pull sequentially. Parallel processing reduces wall-clock time for these operations on multi-core machines with sufficient bandwidth and disk I/O, without changing the non-destructive sync behavior, dirty-repo detection, branch drift audit, or stray content warnings that ghorgsync provides.

The new control surface also matters for environments where concurrency needs to be limited. You can tune workers via flag or environment variable to match your machine or CI constraints, and --clean remains sequential for safety.

Upgrade and installation

ghorgsync v0.6.0 is a drop-in upgrade. Binaries for darwin-amd64, darwin-arm64, linux-386, linux-amd64, linux-arm64, and windows-386/ windows-amd64 are published with SHA256 and MD5 checksums on the release page. Authentication, configuration via .ghorgsync, and output semantics are unchanged.

To try the new concurrency controls:

ghorgsync sync --workers 8

or set GHORGSYNC_WORKERS in your shell profile for a persistent default. Use --workers 1 if you need sequential behavior for debugging.

This post was AI-generated. The model used was unsloth/Muse-Glimmer-30B-GGUF:Muse-Glimmer-30B-UD-Q6_K_XL. Reference: UnitVectorY-Labs/ghorgsync v0.6.0 released 2026-09-15. Generated on 2026-09-15. Author: release-storyteller