x
/
nerd-reviewer
Code Issues Proposed changes
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.
5 Commits 1 Branch 0 Tags 2.1 MiB
Python 100%
Go to file
Joshua Harlow ea9a848e8e Add gerritlib to requirements 
We will need a way to plug-in to the gerrit stream
so that we can push comments; this library seems to
be the defacto one to do this (and I have contributed
code to it so I understand mostly how it works).

Change-Id: I485a7e3a72d8d9042ba6da696808b2e29a8bcb2a
 		2015-03-30 23:00:06 -07:00
doc/source Init project 2015-03-27 01:48:05 +03:00
nerdreviewer Init project 2015-03-27 01:48:05 +03:00
tests Init project 2015-03-27 01:48:05 +03:00
.coveragerc Init project 2015-03-27 01:48:05 +03:00
.gitignore Init project 2015-03-27 01:48:05 +03:00
.gitreview Add .gitreivew & fix setup.cfg 2015-03-31 03:47:57 +03: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 Init project 2015-03-27 01:48:05 +03:00
requirements.txt Add gerritlib to requirements 2015-03-30 23:00:06 -07:00
setup.cfg Add .gitreivew & fix setup.cfg 2015-03-31 03:47:57 +03:00
setup.py Init project 2015-03-27 01:48:05 +03:00
test-requirements.txt Init project 2015-03-27 01:48:05 +03:00
tox.ini Init project 2015-03-27 01:48:05 +03: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