<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Practical PRs on CodeGoalie</title><link>https://codegoalie.com/categories/practical-prs/</link><description>Recent content in Practical PRs on CodeGoalie</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 22 Mar 2021 06:45:22 -0400</lastBuildDate><atom:link href="https://codegoalie.com/categories/practical-prs/index.xml" rel="self" type="application/rss+xml"/><item><title>Magic PR Journeys</title><link>https://codegoalie.com/posts/magic-pr-journeys/</link><pubDate>Mon, 22 Mar 2021 06:45:22 -0400</pubDate><guid>https://codegoalie.com/posts/magic-pr-journeys/</guid><description>&lt;p>I was recently having a conversation about Pull Request reviews with a colleague
of mine and I mentioned that when I&amp;rsquo;m ready to look at code for a PR, I review
one commit at a time in order. After a confused pause, she asked how I could
get the full context by only looking at one commit at a time. I supposed to her
that perhaps the full context is not what facilitates a better review. Instead,
we should follow the journey the developer who opened the PR has set out for us
through their commits.&lt;/p>
&lt;p>I have many more thoughts on this subject, but I&amp;rsquo;d like to hear yours too. Email
me at &lt;a href="mailto:chris@codegoalie.com">chris@codegoalie.com&lt;/a> and let me know what you think about the above
supposition. Possible? Nonsensical? Outright dumb? :)&lt;/p>
&lt;p>Here&amp;rsquo;s to your next magical PR journey!&lt;/p>
&lt;p>— Chris&lt;/p></description></item></channel></rss>