Assembla has built best in class code review tools into every Git Merge Request.
Merge requests are fundamental to how teams review and improve code on Assembla. Progress on sprints, propose new features, and discuss implementation details before changing your master source code.
Start a new feature or propose a change to existing code with a merge request—a base for your team to coordinate details and refine your changes.
Preview changes in context with your code to see what is being proposed. Easy to read Diffs highlight added, edited, and deleted code right next to the original file, so you can easily spot changes.
Browse commits, comments, and references related to your merge request in a timeline-style interface.
Curious who changed that file before you? With blame you can see how any portion of your file has evolved over time without viewing the file's full history.
On Assembla, conversations happen alongside your code. Leave detailed comments on code syntax and ask questions about structure inline with all of the developers without having to open Slack or an Email client.
If you’re on the other side of the code, requesting peer reviews is easy. Add users to your merge request, and they’ll receive a notification letting them know you need their feedback.
Save your teammates a few notifications. Bundle your comments into one cohesive review, then specify whether one, two or more developers must vote on the merge request before it can be merged.
You can’t always avoid conflict even with Git. Merge code faster by resolving simple merge conflicts on Assembla-- no command line necessary.