Released on April 21, 2026, gitrepoforge v0.2.0 marks a significant step forward in how teams manage consistency across their Git repositories. This release focuses on providing better visibility into proposed changes and introducing a more flexible system for automating the application of standards, making the tool safer and more adaptable for large-scale operations.

What’s new

Preview Changes with report

One of the most requested features, the new report command, allows you to see exactly what changes gitrepoforge would make across your entire workspace before any files are actually modified. Instead of scrolling through repetitive logs, the report command generates a clean Markdown summary that deduplicates identical diffs across multiple repositories, giving you a clear, systemic view of the required updates.

Configuration Validation via schema

To reduce “configuration friction,” we’ve introduced the schema command. This tool generates a JSON Schema for your per-repo configuration files based on your central definitions. By integrating this schema into your IDE or CI pipeline, you can catch configuration errors instantly, ensuring that every repository adheres to the intended standard without manual trial and error.

Flexible Automation with Named Actions

The apply command has evolved. You can now define multiple automation profiles—which we call “Named Actions”—within your central configuration. Whether you need a “dry-run” for testing, a “feature-branch” workflow for cautious rollouts, or “direct-main” for urgent fixes, you can now switch between these profiles at runtime using the --action flag.

Why it matters

For organizations managing dozens or hundreds of repositories, the distance between “detecting drift” and “fixing it” can be precarious.

The report command closes this gap by providing a safe, auditable preview, removing the anxiety of bulk-applying changes. Meanwhile, the schema command brings professional-grade validation to your configuration, shifting error detection from the execution phase to the authoring phase. Finally, the move to Named Actions recognizes that automation isn’t one-size-fits-all; it gives platform engineers the precision to control exactly how changes are committed and pushed based on the context of the release.

Upgrading to v0.2.0

Important Behavior Change: To prioritize safety, the apply command no longer performs writes or Git automation by default. If you run apply without specifying an action, it will now behave like the validate command, reporting drift without modifying any files.

To actually apply changes, you must:

  1. Define your automation profiles in the action section of your .gitrepoforge-config file.
  2. Execute the command specifying the desired action: gitrepoforge apply --action <your-action-name>

We recommend reviewing the updated documentation in the docs/commands/ directory to familiarize yourself with the new workflow.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. Reference: UnitVectorY-Labs/gitrepoforge, release v0.2.0, generated on 2026-04-21. Author: release-storyteller