Pull requests are in most regards the base Unit of Work of a software developer. It’s an imperfect metric, for sure, but it is one that is transverse to most projects and areas, be it mobile apps, complex backend APIs, LLMs, or simple documentation repos.

The PR is also the first public showing of our work, specially true on a remote work setting. As authors, we should take great care in it’s clarity of intent (why) and solution (how), and most importantly be receptive to critique. There is much more to be said about PRs and the internet is full of tips, strategies, templates, etc.. but this article is a good place to start.

https://dev.to/karaluton/a-guide-to-perfecting-pull-requests-2b66