Released on May 2, 2026, ghorgsync v0.3.1 brings a significant improvement to how you target GitHub organizations for synchronization. By introducing dynamic overrides, this release removes the rigidity of configuration files, making the tool more adaptable for developers who juggle multiple organizations or automate their workflows.

What’s new

The headline feature of v0.3.1 is the ability to specify your target GitHub organization on the fly. While the .ghorgsync configuration file remains a convenient way to set your defaults, you now have two powerful ways to override it:

  • The --org Flag: You can now explicitly set the target organization directly in your command: ghorgsync --org my-org-name.
  • The GITHUB_ORG Environment Variable: For a more seamless integration with your shell or CI environment, the tool now recognizes the GITHUB_ORG variable.

To ensure there is no ambiguity, ghorgsync follows a strict priority order when determining which organization to sync:

  1. The --org command-line flag (Highest priority)
  2. The GITHUB_ORG environment variable
  3. The organization field in your .ghorgsync config file (Lowest priority)

Why it matters

For many users, a single static configuration file is limiting. If you contribute to several different organizations or need to rotate targets frequently, editing a YAML file every time is a friction point.

By allowing CLI and environment overrides, ghorgsync becomes a first-class citizen in CI/CD pipelines. You can now parameterize your synchronization scripts using environment variables, allowing the same pipeline to sync different organizations based on the context of the build. It simplifies your workflow, reduces the risk of accidentally committing organization-specific config changes, and provides the flexibility needed for professional GitHub management.

Upgrade and Installation

Upgrading to v0.3.1 is straightforward. Use the following Go command to install the latest version:

go install github.com/UnitVectorY-Labs/ghorgsync@latest

This release is fully backward compatible, so your existing configurations will continue to work exactly as before.

This post was AI-generated by release-storyteller using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL on May 2, 2026, based on the v0.3.1 release of UnitVectorY-Labs/ghorgsync.