perf(server): Git status reads a branch's recorded base with one git process, not three - #28778

Eligibility
Branch-base configuration is read with one Git process instead of up to three, preserving existing precedence and fallback behavior. The change is confined to local configuration reads, with no change to product defaults or configuration writes.

Additional Thinking

Your Custom Policy

Default approvability criteria apply. The assessed change neither changes product defaults nor adds or broadens diagnostic-suppression directives, so neither additional human-review condition is triggered.

Code

Consolidates three branch-base configuration reads into one read-only Git invocation. Shared status/base-resolution and publishing lookup callers use the helper, retaining preferred-key and legacy fallback precedence. Branch names are regex-escaped; configuration writes and base-selection rules are unchanged. The customer-ignored file was not reconstructed.

Review Context

Author is only21mil; no code-ownership requirement was supplied. No unresolved review comments or correctness findings were supplied, nor a blocking-severity configuration or independent CI results. The PR description reports identical status outputs across paired measurements and focused test coverage; these are author-reported evidence, not independently verified checks.

Verdict

The understood change reduces local read-only subprocess work while preserving existing selection behavior. It introduces no new external operation, destructive action, or material product-policy decision requiring human judgment.

Notes:
No code owners found in target merge base 1d626d0

Agent Credits: 30 credits
Approvability runs at a flat rate of 30 credits whenever the agent is asked for a verdict.