Code Review Can Be Better

The text explores the challenges and limitations of the current code review processes on platforms like GitHub, particularly the lack of support for stacked pull requests and the inefficiency of remote web interfaces. The author experimented with a tool called git-review, designed to handle code reviews by storing review comments as a single commit on top of the pull request branch, allowing local code modifications and inline feedback. Although this approach initially seemed promising, it encountered practical difficulties with conflict management and integration with existing workflows, leading to a temporary return to traditional web-based code reviews. The text also highlights potential future improvements, such as the adoption of Gerrit-style Change-Id for tracking revisions, and mentions alternative systems like Fossil and git-appraise that may offer better solutions by storing review data within the repository itself. Despite the setbacks, the author remains hopeful that a more efficient and seamless code review process will emerge, inspired by current innovations and existing internal tools used by companies like Jane Street.