Skip to content

feat(proxy): virtual keys naming convention - #8

Merged
fab-siciliano merged 4 commits into
datareply/prodfrom
feature/datareply/virtual-keys-naming-convention
Jul 7, 2026
Merged

feat(proxy): virtual keys naming convention#8
fab-siciliano merged 4 commits into
datareply/prodfrom
feature/datareply/virtual-keys-naming-convention

Conversation

@fab-siciliano

Copy link
Copy Markdown
Collaborator

Relevant issues

Adds #1

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have added meaningful tests
  • My PR passes all CI/CD checks (e.g., lint, format, unit tests)
  • My PR's scope is as isolated as possible; it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Screenshots / Proof of Fix

Type

🆕 New Feature
✅ Test

Changes

@fab-siciliano fab-siciliano changed the title Feature/datareply/virtual keys naming convention feat(proxy): virtual keys naming convention Jul 7, 2026
@fab-siciliano
fab-siciliano merged commit 3d3ed47 into datareply/prod Jul 7, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant