Nope, they still arbitrarily decide to "fold" big changes (file with a large diff), causing me to miss entire files when reviewing on occasion.
In all honesty, their pull request pages need a lot of UX work: too much stuff going on on the overview pages, jumping to unresolved threads does not work when they are in previous commits...
There's also that merge train confusion where merge trains get "cancelled" without an obvious explanation ("this was cancelled because it is included in a new one" would do). In a sense, I'd say that their UX is pretty bad, but the API is not much better either (you can't fetch pipeline log files with individual script timings that you see floating on the right in the web UI). If anything, all of this only goes to show that you don't need to be perfect to be good!
But I applaud the effort, mission and dedication they put up, and especially their open core nature.
In all honesty, their pull request pages need a lot of UX work: too much stuff going on on the overview pages, jumping to unresolved threads does not work when they are in previous commits...
There's also that merge train confusion where merge trains get "cancelled" without an obvious explanation ("this was cancelled because it is included in a new one" would do). In a sense, I'd say that their UX is pretty bad, but the API is not much better either (you can't fetch pipeline log files with individual script timings that you see floating on the right in the web UI). If anything, all of this only goes to show that you don't need to be perfect to be good!
But I applaud the effort, mission and dedication they put up, and especially their open core nature.
Congrats on the IPO and keep pushing forward.