Back to Signal Feed
CodeTracked since May 20, 2026

Mirror missing Git committer env vars from AGOR author vars

Agor now ensures commit identity is set consistently in PR environments by populating missing `GIT_COMMITTER_*` variables from configured `GIT_AUTHOR_*` values, instead of falling back to the executor host’s `~/.gitconfig`. This fixes author/committer splits that caused incorrect multiple PR authors, while preserving any explicitly configured `GIT_COMMITTER_*` settings.

AgorcreateUserProcessEnvironmentGIT_AUTHOR_NAMEGIT_AUTHOR_EMAIL

What Happened

  • Agor now ensures commit identity is set consistently in PR environments by populating missing `GIT_COMMITTER_*` variables from configured `GIT_AUTHOR_*` values, instead of falling back to the executor host’s `~/.gitconfig`. This fixes author/committer splits that caused incorrect multiple PR authors, while preserving any explicitly configured `GIT_COMMITTER_*` settings.
  • Agor now ensures commit identity is set consistently in PR environments by populating missing `GIT_COMMITTER_*` variables from configured `GIT_AUTHOR_*` values, instead of falling back to the executor host’s `~/.gitconfig`. This fixes author/committer splits that caused incorrect multiple PR authors, while preserving any explicitly configured `GIT_COMMITTER_*` settings.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented an explicit env-resolution fix: when `GIT_AUTHOR_NAME`/`GIT_AUTHOR_EMAIL` are present but corresponding committer vars are absent, Agor auto-sets `GIT_COMMITTER_NAME`/`GIT_COMMITTER_EMAIL`; explicit committer vars are never overwritten. Added test coverage for full mirror, explicit override, partial mirror, and no-op behavior.

Why Track This

Why It Matters

Developers and operators using AGOR pipelines will see commits and PR metadata consistently attributed to the intended person, reducing confusion from unexpected committer identities appearing from the execution host and making auditability of contribution history more reliable. Under the hood, the environment resolver now performs identity fallback from missing committer vars to provided author vars, so review workflows should stop showing split authorship; watch whether any legacy jobs still depend on inheriting host `~/.gitconfig` committer settings.

Impact

Developers and operators using AGOR pipelines will see commits and PR metadata consistently attributed to the intended person, reducing confusion from unexpected committer identities appearing from the execution host and making auditability of contribution history more reliable. Under the hood, the environment resolver now performs identity fallback from missing committer vars to provided author vars, so review workflows should stop showing split authorship; watch whether any legacy jobs still depend on inheriting host `~/.gitconfig` committer settings.

What To Watch Next

  • Watch whether Agor becomes a repeated pattern.
  • Track follow-up changes around AI Coding Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: host_gitconfig_dependence_for_committer, mixed_identity_expectations_in_legacy_flows.
Open Topic TimelineOpen Technical EventOpen Original Sourcehost_gitconfig_dependence_for_committer / mixed_identity_expectations_in_legacy_flows / explicit_committer_override_regression

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

preset-io/agor PR #1227: fix(env): mirror GIT_AUTHOR_* to GIT_COMMITTER_* when committer not set

`createUserProcessEnvironment()` now mirrors set `GIT_AUTHOR_*` variables to unset `GIT_COMMITTER_*` variables so commits inherit the intended author identity in AGOR sessions.