Nerd Reviewer bot reviews patches and checks that they pass common project rules e.g. unit test coverage, max amount of loc, well written commit message... So core reviews can concentrate on other more important stuff.

Go to file

Jenkins c89c561514 Merge "Update .gitreview for new namespace"		2017-01-20 18:56:29 +00:00
doc/source	Init project	2015-03-27 01:48:05 +03:00
nerdreviewer	Merge "Begin to add initial scanner modules"	2016-01-18 23:05:37 +00:00
tests	Init project	2015-03-27 01:48:05 +03:00
.coveragerc	Get this repo working again	2016-01-16 23:19:02 -08:00
.gitignore	Init project	2015-03-27 01:48:05 +03:00
.gitreview	Get this repo working again	2016-01-16 23:19:02 -08:00
.testr.conf	Init project	2015-03-27 01:48:05 +03:00
LICENSE	Initial commit	2015-03-17 20:42:48 +03:00
README.rst	Get this repo working again	2016-01-16 23:19:02 -08:00
requirements.txt	Begin to add initial scanner modules	2016-01-17 12:11:27 -08:00
setup.cfg	Get this repo working again	2016-01-16 23:19:02 -08:00
setup.py	Init project	2015-03-27 01:48:05 +03:00
test-requirements.txt	Get this repo working again	2016-01-16 23:19:02 -08:00
tox.ini	py34->py35	2016-12-16 14:24:26 +01:00

README.rst

NerdReviewer - automates dull daily routine code reviews

Nerd Code Reviewer analyzes commits and tell authors where and why they code won't pass human code review process.

Such automation optimizes work on open source projects and simplifies life of new contributors, because they will get interactive step by step guide how to make their patches attractive for project's maintainers.

American Gothic