|
|
|
|
|
by dewiz
2855 days ago
|
|
thanks for reminding me about this, I tried it a while back but eventually abandoned it, because of complex UI (lack of file tree on the side; the file matrix at the top doesn't make it easier to keep status; many buttons don't have a onmouseover tip so it's not clear what they, e.g. if the cause some state change; UI very different from GitHub leading to extra friction with team members) and the noise it generates in GitHub, for users who uses just GitHub |
|
As for GitHub integration, I agree it's not ideal but it's the best their slightly brain-dead review API will allow. Getting the whole team to adopt the tool is much better, but is obviously quite a bit harder. Though that's probably why I'm seeing a lot more success in the enterprise space, where top-down diktats are par for the course.