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.
I'd like to have branch name totally lowercase. This way it would be more friendly on cli tools.
This is to help people that for whatever reason don't want to go through the effort of changing it manually every time.
Default levels of understanding and thoroughness for both positive (review)and negative(flag) could also be configurable in the user-config 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:
diff-mode, the parent of github-review-mode supports outline mode to show/hide hunks while inside the buffer. It seems like github-review-mode somehow broke this.
Always ready to code - spin up fresh, automated dev environments for each task, in the cloud, in seconds
Automated code reviews to help developers ship better software, faster
Automatic test report merging for all CI and languages into a single code coverage report directly into your pull request
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
Pull Assistant analyses pull requests and provides the optimal way to perform code reviews
CommitCheck ensures your commit messages are consistent and contain all required information
AI powered code review and analysis
Improve the security, performance, and maintainability of your Django code
A Benchmarked Definition of Done for Code Quality with BetterCodeHub
Policy enforcement solution for confident and compliant code
Expert On-Demand Code Review as a Service
DO NOT MERGE – as a service
Insert a public link to a Lucidchart diagram so team members can quickly understand an issue or pull request
Code Quality, Code Reviews and Technical Debt evaluation made easy
Identify and fix bug risks, anti-patterns, performance issues, and security flaws using static analysis
Many repositories need to fix, so please help if you like.
If you could help, it would be helpful if you could comment before starting the work not to overlapping.
Fix example
Run exit command after lint.