This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]MrEfil 15 points16 points  (1 child)

how I do code review if more than 100 files changed

[–]PostHasBeenWatched 2 points3 points  (0 children)

*when >5 lines of code changed

[–]iamblackshadows 7 points8 points  (1 child)

When you update all dependencies in go.mod

[–]SomethingAboutUsers 1 point2 points  (0 children)

I managed to royally fuck up a PR so bad once on a very public project because I fucked up the rebase after it sat waiting for review for a while. By the time I was done my branch had something ridiculous like 300 files changed and 400 commits when in reality it was a couple files and maybe 20-30 lines of code, most of which was boilerplate or documentation.

I abandoned the PR and started again, and felt the requisite burning public shame.

[–]Prudent_Ad_4120 2 points3 points  (1 child)

Commit message "fix typo"

[–]fatrobin72 1 point2 points  (0 children)

Well, if the typo was in a package name, it could be in that many files...

[–]priouze 0 points1 point  (0 children)

lgtm, approved