This content originally appeared on Go Make Things and was authored by Go Make Things
Last week, I wrote about my experience working with the team at Cloud Four, and in particular some of their great practices around PR management.
Today, I wanted to talk specifically about a habit my friend Gerardo Rodriguez got me into: reviewing your own pull request.
It’s pretty simple.
When you create a pull request in GitHub, click on the Files changed tab, and scroll through the diff. Anywhere you’ve done something new that’s not already explained by in-code comments, add a comment in the GUI about what you did and why.
- Often, it’s stuff that’s not important enough for in-code commentary, but is useful for the reviewer to know.
- Sometimes, it’s stuff that should actually be documented in the code, and this is a good time to go back and add it.
- Every now and then, you’ll notice a bug in your own code because you’re reading it with fresh eyes, in a different format than your text editor.
It’s a simple behavior change that adds maybe 5 or 10 minutes to the time it takes to setup a PR, but it’s saved me so many headaches, and makes life for whoever reviews your PR a lot easier, too!
Like this? A Lean Web Club membership is the best way to support my work and help me create more free content.
This content originally appeared on Go Make Things and was authored by Go Make Things
Go Make Things | Sciencx (2025-11-11T14:30:00+00:00) Review your own git pull requests. Retrieved from https://www.scien.cx/2025/11/11/review-your-own-git-pull-requests/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.