Pricing Overview
10 users$10 |
25 users$1,800 |
50 users$3,300 |
100 users$6,000 |
500 users$12,000 |
500+ users |
Take the Stash Feature Tour
Branch or Fork Merging
Code changes can be made in isolation and reviewed before being integrated with the mainline. Once a branch or fork is ready for primetime – typically after a bug is fixed or a feature is implemented – Stash's pull requests facilitate the process of merging.
Light-weight Code Review
Pull requests encourage peer review and get teams talking about their code.
Commenting on code in-line (and in context) prompts contributors to review their work and make changes. If changes are made while a pull request is still open, Stash will recognize that and alert reviewers. More collaboration means better code quality!
Approval Process
Multiple team members can be selected to review a pull request, delegating the approval to key stakeholders. Reviewers are notified via email, though the pull request remains visible to all team members so everyone can contribute.
Per-branch Permissions
Branch permissions let you select a "gatekeeper", typically a senior developer, who is responsible for ensuring that the code going into production has been properly tested and reviewed. Stash notifies the gatekeepers of new changes, giving them control over whether, and when, the code is ready to be merged to the stable branch.
Pull Request Conditions
Enforce certain quality requirements and ensure they are met before a pull request can be merged. Set per-repository checks to control when a pull request can be merged. Whether you require a minimum number of reviewers approving a request or a green build, pull requests cannot be merged if the required conditions have not been met.
Review Activity
Once a pull request is created the activity dashboard displays the entire history of a pull request and provides real-time updates on status changes, comments, and code updates. Understand, chronologically, what happened and why, reducing overhead and saving time when reviewing code.
