-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR review #129
Comments
Good observation @li-s . The points in the following link sort of touches on that situation. Have a look and post here if you have further doubts. |
So for each coding violation that is the same, I should just write "I noticed this issue as well"? It seems like it will clog the comments section. |
Hi @damithc , I have this issue as well, when the repo I am reviewing also commits many of the same mistake. After reading the Best practices for reviewing PRs, I still did not find the answer I am looking for. |
Ok thanks, so I just wite that line. |
Hello guys, I have a quick question.
If reviewing PR, and the code has multiples of the same mistake (eg. wrong indent for multiple files), do we flag every single mistake, or just flag one? I'm thinking that if you flag every mistake, it will just make the other member angry at why you are focusing on such minor mistakes.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: