Yes! Gitlab's offerings are great, and our team doesn't even scratch the surface of what's possible with its feature set.
That said, MRs with over 1000 lines of changes are painful sometimes impossible to review. Even small MRs feel clunky, due to how many panels there are (yes, I know they're collapsible). Because MRs are one of our most used features, it sometimes makes me consider switching to GitHub for their much nicer PR UX/UI.
yeah there seems like there is some web -> idea connection that should exist for super slick in-IDE reviews. Best reviews means most context, IDE has the most context about the code (is why its best to resolve merge conflicts too) so we should be leveraging it more.
Always surprised to see people resolving merge conflicts anywhere other than their IDE, IDE has the most knowledge about the inputs to the merge and your chosen resolution, why would you ignore that important info? (like.. does the resulting file compile? for ex..)
Would be very curious about your thoughts on Reviewpad (https://reviewpad.com). The interactions you have on the IDE are very different than a tool that was specifically made for code reviews.
Yeah, I should really quit struggling with Gitlab's.
For really large MRs, I use Tower + Kaleidoscope to view the changes. But then I can't easily leave a comment on a line of code (a big part of the review process)
That said, MRs with over 1000 lines of changes are painful sometimes impossible to review. Even small MRs feel clunky, due to how many panels there are (yes, I know they're collapsible). Because MRs are one of our most used features, it sometimes makes me consider switching to GitHub for their much nicer PR UX/UI.