<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Code-Review on wid's blog</title><link>https://wid-blog.github.io/en/tags/code-review/</link><description>Recent content in Code-Review on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 30 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub PRs and the Code Review Cycle</title><link>https://wid-blog.github.io/en/posts/tech/devenv/github-pr-and-code-review/</link><pubDate>Sun, 30 Nov 2025 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/devenv/github-pr-and-code-review/</guid><description>Looking at GitHub PRs as a collaboration layer on top of Git&amp;rsquo;s change graph, and walking through the Code Review cycle, PR-level design, and merge strategies.</description></item></channel></rss>