Difference between revisions of "Code review"

From Software Heritage Wiki
Jump to navigation Jump to search
(Undo revision 1550 by Vlorentz (talk))
Tags: Redirect target changed Undo
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This page documents code review practices used for [[Software Heritage]] development.
+
#REDIRECT [[swhdocs:devel/contributing/code-review.html#code-review]]
 
 
== Implementation ==
 
 
 
See [[Code review in Phabricator]].
 
 
 
== Good reads ==
 
 
 
Good reads on different angles of code review:
 
 
 
* '''[https://medium.com/palantir/code-review-best-practices-19e02780015f Best practices]''' (Palantir) ← comprehensive and recommended read, especially if you're short on time
 
* [https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines Review checklist] (Code Project)
 
* [https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/ Motivation: team culture] (Google & FullStory)
 
* [https://blog.codinghorror.com/code-reviews-just-do-it/ Motivation: code quality] (Coding Horror)
 
* [http://www.processimpact.com/articles/humanizing_reviews.pdf Motivation: humanizing peer reviews] (Wiegers)
 
  
  
 
[[Category:Software development]]
 
[[Category:Software development]]

Latest revision as of 12:44, 31 March 2021