How I got my first pull request merged into LiteLLM
My first contribution to LiteLLM , the open-source LLM gateway, was PR #38591 . It fixed a bug where content an agent had retrieved was compressed again and lost, which made agents loop. It was merged. If you want to make your first open-source contribution, the short version is: pick a project you already use, reproduce one specific bug, fix only that bug, and let the project's CI teach you its…
My first contribution to LiteLLM, an open-source LLM gateway, was PR #38591. It corrected a bug where content an agent had retrieved was re-compressed, causing agents to loop. To make your first open-source contribution, pick a project you already use, fix a specific bug, and let the project's CI teach you its standards. The bug affected LiteLLM's compression of long context before sending it to a model.
When an agent asked for the full content, it received the same reference again through compression, leading to a loop or an empty response. The fix involved preventing re-compression of content retrieved in client-side tool loops. Finding something to work on is easiest when you're already using the project and encounter a problem.
Start from your own friction, reproduce the bug locally, and check if it has been claimed. Let the CI/CD teach you its standards through linting, type checks, and a large test suite. Keep PRs small, one bug and one fix, and explain the failure and test details. Respond quickly to review comments. After that first PR, more contributions became easier. The best part was realizing a small, careful fix to a widely used project is within reach.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
