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 32 public repositories matching this topic...
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 :).
We'd like to measure the quality of apps written in PHP.
There are "component detectors" to determine frameworks, platform, and type of an application.
It's necessary to implement PHPComponentDetector the similar way as is JavaComponentDetector implemented.
More info in [our Contribution guid
-
Updated
Jun 11, 2020 - TypeScript
-
Updated
Oct 12, 2018 - TypeScript
-
Updated
May 1, 2020 - TypeScript
-
Updated
Mar 14, 2020 - TypeScript
-
Updated
Jun 6, 2020 - TypeScript
The discussions button in the toolbar is a toggle, so it should use the pressed property so it is styled properly when activated/deactivated.
Example:
-
Updated
May 25, 2020 - TypeScript
-
Updated
Apr 29, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
May 22, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Mar 30, 2018 - TypeScript
Proposal:
Modify the check for description at https://github.com/loadsmart/peril-settings/blob/master/rules/common/needsDescription.ts to consider our pre-made PR description templates as if it was empty.
Reasoning
A lot of people forget to fill the templates and send PRs for review without the proper information. Unfortunately, having the template means the check for description w
-
Updated
Jun 3, 2020 - TypeScript
-
Updated
Mar 5, 2018 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Mar 14, 2018 - TypeScript
-
Updated
Jan 2, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Jun 3, 2020 - TypeScript
-
Updated
May 21, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
-
Updated
Jun 4, 2020 - TypeScript
- Wikipedia
- Wikipedia
Related Topics
gerritCode review apps
DeepScan
Advanced static analysis for automatically finding runtime errors in JavaScript code
Sider
Automatically analyze pull request against custom per-project rulesets and best practices
DeepSource
Discover bug risks, anti-patterns and security vulnerabilities before they end up in production. For Python, Go and Ruby
Datree
Policy enforcement solution for confident and compliant code
Coveralls
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
gitpod.io
Online IDE for GitHub
Code Inspector
Code Quality, Code Reviews and Technical Debt evaluation made easy
AccessLint
Find accessibility issues in your pull requests
WIP
DO NOT MERGE – as a service
Pull Assistant
Pull Assistant analyses pull requests and provides the optimal way to perform code reviews
Review Notebook App
Code review for Jupyter Notebooks with visual diff & commenting
codebeat
Code review expert on demand. Automated for mobile and web
Mergify
Pull requests automation service
Code Climate
Automated code review for technical debt and test coverage
Better Code Hub
A Benchmarked Definition of Done for Code Quality with BetterCodeHub
The GitHub Integration just fails with a GitHub Error Response if your Issue Comment gets too long.
It’d be great if we truncated the message, & added a📝 ?
[truncated]Thoughts @orta ? I’m happy to implement this if you have advice!