Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
codeapprove
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
codeapprove
5y ago
If you view code reviews as expressing a lack of trust, you're probably doing them wrong. Code reviews should be a conversation among people who trust each other. You're saying "hey I'd like to know your thoughts about t
62.
▲
by
codeapprove
5y ago
This is a really cool and thorough approach. I've always thought that it's strange how programmers are extremely picky when it comes to tools for wiring code but they seem to accept whatever they're given for reviewing code.
63.
▲
by
codeapprove
5y ago
Good idea, thank you!
64.
▲
by
codeapprove
5y ago
Almost everyone agrees that code review is important and worth spending time on, so why don't we think much about our code review tools? Most of us just accept whatever GitHub gives us (esp. smaller or newer teams) I'm building Co
65.
▲
by
codeapprove
5y ago
CodeApprove is a better code review tool for teams on GitHub: https://codeapprove.com The frontend is Vue 2.0 and TailwindCSS. No other major libraries besides the Vue standards (router, store, etc). The site is delivered by Fir
66.
▲
by
codeapprove
5y ago
Hi HN, CodeApprove is a better way to review Pull Requests on GitHub. I love GitHub but the code review tools are not as good as what's available to big companies with self-hosted tools. Many of us put up with GitHub's PR reviews
67.
▲
Show HN: CodeApprove – better code review for teams on GitHub
(codeapprove.com)
17 points
by
codeapprove
5y ago
|
1 comments
68.
▲
by
codeapprove
5y ago
Shameless plug: if your team uses Pull Requests but finds GitHub code reviews to be somewhat painful, I'm building https://codeapprove.com to solve your problems. I think with the right tools and processes GitHub PRs are an
69.
▲
by
codeapprove
5y ago
I'm building a much better code review for tool for GitHub, check out https://codeapprove.com It combines concepts from GitHub, Gerrit, and other good review tools out there to make it easy and fast to reach consensus (whic
70.
▲
by
codeapprove
5y ago
That's a shame, heard only good things about those tools. Shameless but timely plug: I'm building a much better code review tool for teams on GitHub. Check out https://codeapprove.com and if you're interested to h
71.
▲
by
codeapprove
5y ago
I built https://codeapprove.com because I love GitHub but I don't love Pull Request reviews. I wanted to make a drop-in replacement for code review on GitHub that made reviews much more structured and focused while not requ
72.
▲
by
codeapprove
5y ago
I love this article, clearly you and your team have thought deeply about the process of code review and Pull Requests. By having strong principles you make sure you're not dominated by the process. I actually don't think Pull Requ
73.
▲
by
codeapprove
5y ago
At all of the big companies I’m aware of (FAANG big) code review is done by peers. There’s no central code review “team”, every single change must be reviewed by one or more peers depending on who owns that part of the codebase. Some compan
74.
▲
What is the point of code review?
(medium.com)
1 points
by
codeapprove
5y ago
|
0 comments
75.
▲
by
codeapprove
5y ago
Yep can do a demo or even just get you set up to explore. Send me an email (sam at habosa dot com) and I’ll find a time for us to chat.
76.
▲
by
codeapprove
5y ago
I’m building a much better tool for reviewing code on GitHub. Still in early stages and looking for feedback, but our central idea is exactly what you mention. We make sure that all comments are resolved before the review is done and help y
77.
▲
by
codeapprove
5y ago
I do agree that the process of comitting, pushing, and opening a PR can be a bit clunky. But I also think PRs are super valuable because they encapsulate code and discussion in one place that's easy to reference in the future. If I fin
78.
▲
by
codeapprove
5y ago
I totally agree with all of this! Especially "be your first code reviewer" which is something I find very helpful. Seeing my own code in the same interface that my reviewer will use helps me get a different perspective and spot so
79.
▲
by
codeapprove
5y ago
I'm building a better interface for code review for teams on GitHub, one that helps you reach consensus quickly and decisively. If anyone here is interested please email me at sam@habosa.com
80.
▲
by
codeapprove
5y ago
This is a great article and I'd like to shamelessly plug my product, which is designed to make code review better for teams that work on GitHub You can look at https://codeapprove.com for an idea of where we're going b
81.
▲
by
codeapprove
6y ago
I really like this terminology! I might see if my team could use this, I've found that not everyone interprets code review comments the same way. I'm working on a new tool to vastly improve human code reviews for teams on GitHub.
82.
▲
by
codeapprove
6y ago
Very cool! I think these types of automations are great for exactly the reason you said: helping reviewers focus on the meaningful changes and not bikeshedding. I am building a tool to make _human_ reviews on GitHub much better and more pow