Introducing Monty 1.0, the Feedback Helper

One of the biggest challenges of Code Review is providing good, useful feedback. The kind that’s clear, straight to the point, and doesn’t turn a code review into a battlefield. The tools help us make changes visible, understand them and estimate their impact on the project, they also help us find problems easier and faster. Yet they provide zero help when we need to find the right words to comment on the problem. No help at all. That is, they didn’t, up until now.

We are happy to introduce Monty, a plugin to Upsource that allows you to significantly reduce the amount of poorly worded unclear feedback in the comments, thus making your code review discussions even more productive! Your team can now collaborate on the code base with an entirely new level of understanding.

Once you’ve installed the plugin, the only thing you need to do is to enable “Feedback analysis” option in your project’s settings. That’s it!

Now, whenever you type a comment that is rude, unclear, or has other issues, Monty will highlight the problem for you and suggest corrections. For example:
monty1

Monty can even help your team with more subtle communication problems.
monty2

In most severe cases Monty disables the “Add comment” button.
monty4

Want to improve communications in your team? Download and install the plugin today!
If you have any questions, feature suggestion or problems, feel free to send your feedback to us, preferably after it has been looked at by Monty 😉

Yours truly,
The Upsource Team

This entry was posted in Feature. Bookmark the permalink.

8 Responses to Introducing Monty 1.0, the Feedback Helper

  1. A.T. says:

    This plugin should be enabled over the entire internet!
    Well played. :)

  2. Gregory Hlavac says:

    But how will Linus give feedback if this is in place?!

  3. S.M. says:

    Thanks for the laugh :-) And a lot of forums and Facebook communities could use such a plugin, wouldn’t be the worst idea 😉

  4. Umair says:

    Wow I wouldn’t like to work with the 1st and 3rd devs.

  5. Mike says:

    Make it Atlassian Bitbucket and GitLab compatible

  6. Jan says:

    Good one! Made me smile.

  7. The 2nd example is an example of political correctness gone wrong. To say that is a personal attack is stupid. If the person didn’t write a test, and they are required to do so by the coding standards of the organization or project, is not attacking the person submitting the code, it’s stating a fact.

    I can see that this flag doesn’t prevent the comment from being submitted but what I find annoying is that it was raised to begin with.

    Apart from that, it looks great. Hope github never implements it tho because I would never get to comment on any of the pull requests i deal with. :)

  8. Another year, I fall for another stupid april fools joke. Stupid tradition.

Leave a Reply

Your email address will not be published. Required fields are marked *