Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryThis PR updates
Confidence Score: 5/5Safe to merge — only README marketing copy is changed, with no code, logic, or schema impact. All changes are confined to README.md (documentation/marketing). There are no code, test, schema, or configuration changes, so there is no risk of runtime breakage, data loss, or regressions. No files require special attention.
|
| Filename | Overview |
|---|---|
| README.md | README header rewritten: updated tagline, Railway deploy URL migrated from railway.app to railway.com with new referral/UTM params, Enterprise link updated to litellm.ai/enterprise, Website CTA and GitHub Stars badge added, and Enterprise section gains a "Get an Enterprise License" CTA. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[README.md Header] --> B[Updated Tagline\nOpen Source AI Gateway]
A --> C[Deploy Buttons]
C --> C1[Render Deploy — unchanged]
C --> C2[Railway Deploy\nrailway.app → railway.com\n+ new referral/UTM params]
A --> D[Nav Links]
D --> D1[LiteLLM Proxy Server — unchanged]
D --> D2[Hosted Proxy — unchanged]
D --> D3[Enterprise Tier\ndocs.litellm.ai → litellm.ai/enterprise]
D --> D4[Website CTA — NEW\nlitellm.ai]
A --> E[Badges]
E --> E1[PyPI Version — unchanged]
E --> E2[GitHub Stars — NEW]
E --> E3[YC W23 — unchanged]
F[Enterprise Section] --> G[Get an Enterprise License — NEW\nlitellm.ai/enterprise]
F --> H[Talk to founders — unchanged]
Reviews (2): Last reviewed commit: "update railway url" | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
* week 1 checklist * update railway url
* week 1 checklist * update railway url
Relevant issues
[✅ ]Update README H1
[✅ ] Rewrite opening paragraph
[✅ ] Add website + enterprise CTAs
[✅ ] Add GitHub stars badge
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/test_litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit@greptileaiand received a Confidence Score of at least 4/5 before requesting a maintainer reviewDelays in PR merge?
If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).
CI (LiteLLM team)
Branch creation CI run
Link:
CI run for the last commit
Link:
Merge / cherry-pick CI run
Links:
Type
🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test
Changes