How to Create Better Pull Requests

Connect the pull request to its ticket. If your ticket management system recognizes ticket IDs in pull request titles, use the expected prefix. For example:

LLM-23591: Update model deployment

This makes the relationship easy to discover and may enable automatic linking.

Add a short, useful description. Summarize the pull request in one sentence, but avoid unnecessarily duplicating the ticket. Keep business context and requirements in the ticket. Put implementation details and reviewer specific information in the pull request. This is useful because Git tools and IDE extensions can display pull request descriptions directly, while ticket details usually require opening another system.

Keep the pull request focused. Do not fix unrelated problems simply because you noticed them while working on the main task. Create a separate ticket and pull request instead. A focused pull request is easier to understand, review, test, and revert.

Write code with the difference in mind. Before requesting a review, inspect the difference, not only the final files. Avoid unrelated formatting, unnecessary movement of code, and changes to untouched lines. When two implementations are equally clear, prefer the one that produces a smaller, more focused difference. However, do not sacrifice the quality of the final code merely to reduce the number of changed lines.