>open a PR>clean CI run, tests all good, one approval already>no action for days from the second reviewer>finally hear from his lazy ass>"This has merge conflicts now."
>>109939340it's your job to have the no conflicts if you didn't get it merged in time YOU lazy ass.
>>109939539There's always at least one nigger on the team anywhere who uses reviews to make sure he wins all the races to merge because he has a panic attack any time git tells him there's a merge conflict. Sounds like it's you.
>>109939340Has happened to me before, with some PRs taking weeks to be reviewed.Crazy stuff, I felt like the whole team was like >>109939653 described.
>not using AI to do code reviews.why even bother?