Start with a 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.

Submit your changes

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.

See every change.


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.

Code Blame

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.

Discuss code changes.


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.

Request reviews

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.

Review permissions

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.

Resolve simple conflicts (coming soon)

You can’t always avoid conflict even with Git. Merge code faster by resolving simple merge conflicts on Assembla-- no command line necessary.

Ensure the highest quality code.

Code reviews can improve your code, but mistakes happen. Limit human error and ensure only high quality code gets merged with detailed permissions, source code scanning and branch management.


Give collaborators as much access as they need through your repository settings. You can extend access to a few teams and select which ones can read or write to your files.

Protected branches

Protected Branches help you maintain the integrity of your code. Limit who can push to a branch, and disable force pushes to specific branches.

Source Code Analysis

Every year, companies release new software and are surprised by a zero day attack. When teams address security vulnerabilities at the source code level, it can prevent attacks like this from happening. At Assembla, we offer an automated vulnerability scan, seamlessly integrated with your SDLC.

Bullet-proof your review process

Integrate your code review with Jenkins continuous integration to avoid human error and add extra polish to your team’s code. Automatically run functional tests and let Jenkins vote on the code for you.

Deploy your apps to the cloud

Whether it’s AWS, Azure or Google deploy your code to the container of your choice and ensure your code deploy goes smoothly. Monitor for issues and revert your deployment automatically if problems arise.