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 16 public repositories matching this topic...
With a .stylelintrc.json file with:
{
"extends": [
"stylelint-config-sass-guidelines",
"stylelint-config-prettier"
],
...
}
I get this error:
Error: Could not find "stylelint-config-sass-guidelines". Do you need a `configBasedir`?
at module.exports (/home/linters/app/node_modules/stylelint/lib/utils/configurationError.js:8:28)
at getModulePat
-
Updated
Nov 4, 2019 - Ruby
-
Updated
Feb 12, 2019 - Ruby
cody replace second_level ==> picks a different random reviewer from the group
Hi, @hanneskaeufler! Thanks for your awesome plugin.
We are using it inside our review pipeline with great success: https://github.com/wemake-services/kira-review
But, I would like to suggest adding a very useful feature: clickable filenames and lines.
When I review current TODOs I have to go inside the code manually, find the correct line, and then go back again.
<img width="501" alt="Сни
-
Updated
Mar 1, 2017 - Ruby
-
Updated
Feb 8, 2017 - Ruby
-
Updated
Jul 18, 2018 - Ruby
Is your feature request related to a problem? Please describe.
Right now, the only way to link a PR in an issue is by using the link.
Describe the solution you'd like
A better way would be to link it with the ID of the PR. Maybe detect and add link when PR#32 is detected?
Describe alternatives you've considered
N/A
Additional context
See how Redmine allow various ite
-
Updated
May 30, 2018 - Ruby
-
Updated
Apr 24, 2020 - Ruby
-
Updated
Oct 20, 2017 - Ruby
-
Updated
Jun 6, 2020 - Ruby
- Wikipedia
- Wikipedia
Related Topics
gerritCode review apps
DeepSource
Discover bug risks, anti-patterns and security vulnerabilities before they end up in production. For Python, Go and Ruby
Lucidchart Connector
Insert a public link to a Lucidchart diagram so team members can quickly understand an issue or pull request
Pull Assistant
Pull Assistant analyses pull requests and provides the optimal way to perform code reviews
WIP
DO NOT MERGE – as a service
Coveralls
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
codebeat
Code review expert on demand. Automated for mobile and web
gitpod.io
Online IDE for GitHub
Review Notebook App
Code review for Jupyter Notebooks with visual diff & commenting
Datree
Policy enforcement solution for confident and compliant code
Code Inspector
Code Quality, Code Reviews and Technical Debt evaluation made easy
Mergify
Pull requests automation service
AccessLint
Find accessibility issues in your pull requests
Codecov
Group, merge and compare coverage reports
Hound
Automated code reviews
Sider
Automatically analyze pull request against custom per-project rulesets and best practices
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 (
buildjob) 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