Code review
Code review is systematic examination (sometimes referred to as peer review) of computer source code. It is intended to find mistakes overlooked in software development, improving the overall quality of software. Reviews are done in various forms such as pair programming, informal walkthroughs, and formal inspections.
Here are 209 public repositories matching this topic...
-
Updated
Mar 10, 2020
reviewdog/reviewdog#405 introduced the -tee
option, but there is no mention of the feature in the readme. This would be helpful info for us who are trying to implement/debug this tool
According to houndci/hound#1756, Hound CI supports a curated list of Rubocop extensions. However, it is difficult to tell which extensions are available, and which are not.
Please list supported Rubocop extensions on documentation pages.
-
Updated
Mar 31, 2020 - Python
From @chrisdias:
If I start the auth dance, then press Cancel when asked if I want to let the extension open a URL, the status bar stays at Signing into github.com.... Since I cancelled, I expect it to revert back to Sign in to github.com.
Also (just noticed this) we say into and in to. Not sure which version is right or wrong, or if its based on context :).
Especially in the light of #151 , it would be great if people could just re-generate the whole Id file.
-
Updated
Mar 30, 2020 - Python
-
Updated
Aug 6, 2019
-
Updated
Feb 7, 2020 - JavaScript
-
Updated
Mar 9, 2020
After reading the README.md it's still unclear to me whether it's possible to review / vote on Gerrit changes whose project I have not cloned to a local Git repository (and thus have also not configured them in IntelliJ).
The REDAME.md says "By default, you will only see changes to Git repositories that are configu
-
Updated
Nov 28, 2017 - PHP
-
Updated
Oct 8, 2017 - JavaScript
It might be useful to highlight tab characters (if only for Makefiles).
Also git allows to highlight trailing whitespaces, which is lost in diffr (because we trim all color codes).
-
Updated
Nov 4, 2019 - Ruby
-
Updated
Mar 24, 2020 - CMake
Can we have a flag to disable this line in the logs to reduce noise in policy-bot logs?
2020-03-11T18:28:24.395901944Z |INFO| http_request elapsed=0.238318 method=GET path=/ rid=bpkiri3g83ahlvath4k0 size=1986 status=200```
It would be nice if diff-goto-source
(C-c C-c
) worked when this is invoked from github-review-forge-pr-at-point
. All it needs to do is set the current directory to the git working tree in the diff-mode
buffer. In many cases it does not matter too much whether the user has the "correct" branch is checked out - it just needs to be close.
-
Updated
Mar 23, 2017 - Java
Caused by src-d/lookout#447 (comment)
It is needed to decide how to create PNG versions of SVG to be used in docs (because GitBook does not support SVG).
Currently it is done with a screenshot from mermaid view, but it does not scale and can not be integrated in the CI.
"fix typos" should include file names, or the type of location / change, like "Fix CSS typos" or something.
Also "Minor fixes" could be more descriptive.
Overall,
-
Updated
Mar 5, 2020 - Python
Example for Brakeman
Split from #31
I don't find a checkstyle formatter for brakeman,
https://github.com/presidentbeef/brakeman/blob/master/OPTIONS.md#output-options
So we can use Saddler::Reporter::Github's PullRequestComment.
brakeman -f text \
| saddler report \
--reporter Saddler::Reporter::Github::PullRequestComment
We want the converter from brakeman output to checkstyle.
-
Updated
Sep 22, 2017
Currently, we have provided a list of RepoSense's capabilities in the README.
It may be good to add a sentence describing these features from the user's perspective.
An example
RepoSense is a contribution analysis tool for Git repositories. **It can help educators keep track of work done in student projects, while developers can use it to generate portfolios displaying their open source con
-
Updated
Dec 20, 2018 - JavaScript
- Wikipedia
- Wikipedia
Related Topics
gerritCode review apps
Sider
Automatically analyze pull request against custom per-project rulesets and best practices
Coveralls
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
Pull Assistant
Pull Assistant analyses pull requests and provides the optimal way to perform code reviews
WIP
DO NOT MERGE – as a service
Mergify
Pull requests automation service
Hound
Automated code reviews
Codacy
Automated code reviews to help developers ship better software, faster
DeepScan
Advanced static analysis for automatically finding runtime errors in JavaScript code
Lucidchart Connector
Insert a public link to a Lucidchart diagram so team members can quickly understand an issue or pull request
Review Notebook App
Code review for Jupyter Notebooks with visual diff & commenting
Datree
Policy enforcement solution for confident and compliant code
Code Climate
Automated code review for technical debt and test coverage
Codecov
Group, merge and compare coverage reports
Better Code Hub
A Benchmarked Definition of Done for Code Quality with BetterCodeHub
AccessLint
Find accessibility issues in your pull requests
I cannot figure out how to use properly danger on circleci 2.0 with workflows
Support I have a linear workflow where I bundle my app / install libraries (
build
job) and then run the tests in parallel. (I'm taking Ruby/Rspec as an example).How can I execute Danger to report test failures on all containers ?
Currently if a job fails on circleCI, the dependent jobs are not ran (ie if I