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.
Especially in the light of #151 , it would be great if people could just re-generate the whole Id file.
On the following example:
@
-fn func(a,b,c) {
- x = g(a,b)
- y = if x {
- h(b,c)
- } else {
- 0
- }
- return x + y
-}
+// fn func(a,b,c) {
+// x = g(a,b)
+// y = if x {
+// h(b,c)
+// } else {
+// 0
+// }
+// return x + y
+// }diffr displays the diff like that:
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.
Automated code reviews to help developers ship better software, faster
Advanced static analysis for automatically finding runtime errors in JavaScript code
Find accessibility issues in your pull requests
Code Quality, Code Reviews and Technical Debt evaluation made easy
DO NOT MERGE – as a service
Online IDE for GitHub
A Benchmarked Definition of Done for Code Quality with BetterCodeHub
Automatically analyze pull request against custom per-project rulesets and best practices
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
Automated code review for technical debt and test coverage
Automatic test report merging for all CI and languages into a single code coverage report directly into your pull request
Policy enforcement solution for confident and compliant code
Code review expert on demand. Automated for mobile and web
Pull requests automation service. Merge your pull requests faster
Automated code reviews
Similar to microsoft/vscode-pull-request-github#1622, have the same behavior for the queries in the PR tree