6 views
-/https://github.com/berriai/litellm/issues/30012
GitHub · issue

#30012 Preserve original PR authorship when squashing staging branches into main

  • State: open
  • Author: @Cyberfilo
  • Labels: llm translation

Hi @Sameerlite, thanks for merging my recent PRs.

I noticed that when a dated staging branch is squashed into `main`, the original PR authors are kept only as `Co-authored-by:` trailers and the commit author becomes the maintainer who runs the squash. GitHub's contributors graph and the README contrib.rocks image are author-only, so contributors whose work ships this way never appear there even though their code is in `main`.

For reference, here are my merged PRs and the `main` commits that shipped them (I am credited as co-author on each):

- #28567 jp. Bedrock cross-region opus-4-7 -> shipped in d671a09c20 (Litellm oss staging 050626) - #28575 forward custom_llm_provider through the Responses bridge -> d671a09c20 - #27831 jp. Bedrock cross-region sonnet-4-6 -> d671a09c20 - #28572 EU/AU/JP Bedrock Anthropic 1hr cache pricing -> c7ab9adde5 (Litellm oss staging 030626) - #28569 Vertex AI Anthropic 1hr cache tier -> c7ab9adde5 - #28151 UI pause/resume switch on the models table -> b84f7f82f7 - #27927 blocked flag for model pause/resume -> 492891cad8 - #27832 sanitize empty text blocks on /v1/messages -> f35e7eb2f6 - #28573 us-gov Sonnet 4.5 200k-tier pricing fix - #28574 us-gov Hai…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h16m25s ago — entered · #import:https:::github.com:berriai:litellm post #2568
The right issue is harder because it spans cross-provider request translation, proxy behavior, parameter filtering, and compatibility testing across Azure and Anthropic-style clients. The left issue is comparatively narrower, focused on adjusting release or merge metadata handling and validating contributor attribution.
#0 of 0 · 31d17h59m43s ago — current · #import:https:::github.com:berriai:litellm post #2859
The left issue requires coordinated changes across pricing, token accounting, provider normalization, aggregation, and regression coverage, with backward-compatibility risk. The right issue is primarily a repository workflow and merge-configuration change with limited runtime scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search