<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Review on Time Friend</title><link>https://time-friend.com/en/tags/code-review/</link><description>Recent content in Code-Review on Time Friend</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Wed, 29 Jul 2026 15:15:07 +0800</lastBuildDate><atom:link href="https://time-friend.com/en/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Improving Code Review Efficiency with Husky</title><link>https://time-friend.com/en/archive/husky-code-review/</link><pubDate>Tue, 04 Dec 2018 00:00:00 +0000</pubDate><guid>https://time-friend.com/en/archive/husky-code-review/</guid><description>&lt;p&gt;During code review, code style is one of the review criteria. Reviewing code style involves a certain amount of work.&lt;/p&gt;
&lt;p&gt;To reduce the workload of code review, why not standardize code style before committing?&lt;/p&gt;
&lt;p&gt;This way we can save a lot of time during code review and spend it on more meaningful things.&lt;/p&gt;
&lt;h1 id="git-hooks"&gt;Git Hooks&lt;/h1&gt;
&lt;p&gt;Git provides hooks — mechanisms to trigger other programs when operations like &lt;code&gt;code commit&lt;/code&gt;, &lt;code&gt;push&lt;/code&gt;, etc. occur.&lt;/p&gt;</description></item><item><title>Three Keys to Maintaining Code Review Habits in Your Team</title><link>https://time-friend.com/en/archive/code-review-habits/</link><pubDate>Fri, 30 Nov 2018 14:00:00 +0000</pubDate><guid>https://time-friend.com/en/archive/code-review-habits/</guid><description>&lt;p&gt;We&amp;rsquo;ve talked about code review before. Maintaining a code review habit in a team is quite difficult.
We need proper processes, tools, and institutional support to ensure the efficiency and quality of our code reviews.&lt;/p&gt;
&lt;h1 id="process-support-gitflow"&gt;Process Support: Gitflow&lt;/h1&gt;
&lt;p&gt;We&amp;rsquo;ve introduced the Gitflow workflow before.&lt;/p&gt;
&lt;p&gt;It roughly goes like this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Developers create a dedicated branch in the local repository to develop features.&lt;/li&gt;
&lt;li&gt;Developers push branch changes to the public Git repository.&lt;/li&gt;
&lt;li&gt;Developers initiate a Merge Request through Git.&lt;/li&gt;
&lt;li&gt;Other team members review the code, discuss, and make changes.&lt;/li&gt;
&lt;li&gt;The project maintainer merges the feature into the official repository and closes the Merge Request.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="tool-support"&gt;Tool Support&lt;/h1&gt;
&lt;h2 id="enforce-eslint"&gt;Enforce ESLint&lt;/h2&gt;
&lt;p&gt;Use ESLint strictly. Before code is committed, use tools like husky to enforce ESLint checks.
Ensure that all submitted code passes ESLint first.&lt;/p&gt;</description></item><item><title>Code Review Tool Recommendations and Usage Report</title><link>https://time-friend.com/en/archive/code-review-tools/</link><pubDate>Mon, 12 Nov 2018 00:00:00 +0000</pubDate><guid>https://time-friend.com/en/archive/code-review-tools/</guid><description>&lt;p&gt;As teams grow, unifying coding standards and improving code quality becomes increasingly important. Code review, as one of the effective ways to improve code quality, is worth implementing within the company.
Help the team develop a code review habit, improve code quality, and avoid unnecessary problems in advance.&lt;/p&gt;
&lt;p&gt;For more efficient code review, a code review tool is needed. Hence this usage report.&lt;/p&gt;
&lt;p&gt;Below are some tools I&amp;rsquo;ve tried, along with evaluations and summaries.&lt;/p&gt;</description></item><item><title>How Code Review Helps Teams Improve Code Quality</title><link>https://time-friend.com/en/archive/code-review-quality/</link><pubDate>Thu, 08 Nov 2018 00:00:00 +0000</pubDate><guid>https://time-friend.com/en/archive/code-review-quality/</guid><description>&lt;h1 id="code-review-solutions"&gt;Code Review Solutions&lt;/h1&gt;
&lt;p&gt;Recently, I&amp;rsquo;ve been promoting code review in my company.
After several days of research, I&amp;rsquo;ve compiled some problems and solutions.&lt;/p&gt;
&lt;h2 id="current-problems"&gt;Current Problems&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;No good tool for convenient code review&lt;/li&gt;
&lt;li&gt;No good code standards for code review&lt;/li&gt;
&lt;li&gt;No enforced process for code review&lt;/li&gt;
&lt;li&gt;No dedicated person responsible for code review&lt;/li&gt;
&lt;li&gt;Tracking changes after code review&lt;/li&gt;
&lt;li&gt;Incentive mechanism for reviewers and fixers&lt;/li&gt;
&lt;li&gt;Cross-team resource allocation can lead to excessive code&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="solutions"&gt;Solutions&lt;/h1&gt;
&lt;h2 id="integrate-merge-request-workflow"&gt;Integrate Merge Request Workflow&lt;/h2&gt;
&lt;p&gt;To do code review on GitLab, we need to add Merge Request to our existing Git workflow.&lt;/p&gt;</description></item></channel></rss>