---
type: "post"
id: "commit-rewriter-0-2-analysis-201a04"
slug: "commit-rewriter-0-2-analysis-201a04"
title: "commit-rewriter 0.2 adds support for operating on Git branches other than the repository’s default branch"
description: "commit-rewriter 0.2 moves branch selection from an implicit repository default to an explicit command-line choice."
retrieval_nugget: "commit-rewriter 0.2 moves branch selection from an implicit repository default to an explicit command-line choice."
published_at: "2026-09-25"
updated_at: "2026-09-25"
record_date: "2026-09-25"
date_kind: "published_at"
topics: []
source_urls: ["https://simonwillison.net/2026/Sep/24/commit-rewriter"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:commit-rewriter-0-2-analysis-201a04"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:4439a3782fa9c0aba2fce3ac0974a0226fa70000b6faa3e79e9ccd2f7e444784","reviewed_at":"2026-09-25T06:00:39.409Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":2,"watch_condition_count":2,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"commit-rewriter 0.2 moves branch selection from an implicit repository default to an explicit command-line choice.","observed_facts":[{"text":"The release announces support for branches other than the default branch.","source_urls":["https://simonwillison.net/2026/Sep/24/commit-rewriter"]},{"text":"The documented example is `uvx commit-rewriter --branch other`.","source_urls":["https://simonwillison.net/2026/Sep/24/commit-rewriter"]}],"mechanism":"The mechanism is explicit target selection: the `--branch` argument directs the tool’s rewriting operation to a named branch instead of relying on the default branch.","why_now":"Why now is simply the 0.2 release: this is the first supplied evidence of non-default-branch support.","implications":["The practical implication is that release, maintenance, and long-lived feature branches can be included in an automated rewriting workflow without making the default branch the only supported target.","Scripts can declare the intended branch directly when invoking the tool."],"evidence_boundary":"The evidence boundary is narrow: the announcement does not specify conflict handling, safeguards, compatibility with protected branches, or behavior under concurrent updates.","watch_conditions":["Watch whether later documentation or releases explain those operational limits, especially for automated use on shared branches.","Watch for evidence that branch targeting works reliably in repositories with protected or concurrently updated branches."],"related_records":[],"new_branch_reason":"This starts a distinct analytical record because no prior New Runtime record was supplied; the available related matches do not provide an established record to extend."}
routes: {"html":"https://newruntime.com/posts/commit-rewriter-0-2-analysis-201a04/","markdown":"https://newruntime.com/posts/commit-rewriter-0-2-analysis-201a04.md","json":"https://newruntime.com/posts/commit-rewriter-0-2-analysis-201a04.json"}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
---

# commit-rewriter 0.2 adds support for operating on Git branches other than the repository’s default branch

## Retrieval answer

commit-rewriter 0.2 moves branch selection from an implicit repository default to an explicit command-line choice.

commit-rewriter 0.2 moves branch selection from an implicit repository default to an explicit command-line choice. The release states that branches other than the default branch are now supported, and gives `uvx commit-rewriter --branch other` as the example invocation.

The mechanism is explicit target selection: the `--branch` argument directs the tool’s rewriting operation to a named branch instead of relying on the default branch. That matters because commit-history operations are sensitive to scope; scripts and operators can now state which development line they intend to affect. The practical implication is that release, maintenance, and long-lived feature branches can be included in an automated rewriting workflow without making the default branch the only supported target.

Why now is simply the 0.2 release: this is the first supplied evidence of non-default-branch support. The evidence boundary is narrow: the announcement does not specify conflict handling, safeguards, compatibility with protected branches, or behavior under concurrent updates. Watch whether later documentation or releases explain those operational limits, especially for automated use on shared branches. This starts a distinct analytical record because no prior New Runtime record was supplied; the available related matches do not provide an established record to extend.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)