# Stash Latest (2.12) : Stash 2.2 release notes

Created and last modified by pwatson on Jul 17, 2013

05 March 2013

With today's release of Stash 2.2 we introduce several capabilities for customising your Git development workflow – Git repository hooks, an API for hook integrations, and merge checks for pull requests.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

The Stash 2.2 changelog is at the bottom.

#####

## Git repository hooks

Git hooks allow you to customise your development team's workflow for any requirement they may have. Admins can enable and configure hooks for each repository, right within Stash, without having to install them on the file-system.

Stash comes bundled with repository hooks to let you start customising Stash straight off.

Read more about using repository hooks in Stash.

## API for hook integrations

We've leveraged native Git hooks to create a new hooks API that allows developers to easily write their own hooks. Stash handles the persistence, packaging and per-repository configuration for your hooks, making it simple to extend Stash to suit your particular project's needs. Read more about writing hooks for Stash in our revamped developer docs.

Furthermore, you can mix-and-match bundled Stash hooks with hooks from the Atlassian Marketplace. You can find and install these from within Stash – simply use the Add hook button on the hooks settings page to view available hooks from the marketplace.

## Merge checks for pull requests

To help customise your workflow, you can now set checks to control when a pull request can be merged. Pull requests cannot be merged if the required checks have not been met. These checks are set separately on each repository in a Stash project:

- Require a minimum number of approvers – block merging of a pull request until it has been approved by the selected number of participants.
- Require a number of completed builds – stop pull requests from being merged if they have any unsuccessful builds, and until the set number of builds have completed.

Read more about merge checks in Stash.

## Change log

This section will contain information about the Stash 2.2 minor releases as they become available. These releases will be free to all customers with active Stash software maintenance.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

## 05 March 2013 - Stash 2.2.0

T | Key | Summary
--- | --- | ---
| STASH-3140 | Disable merging until a set number of people have approved the pull request
| STASH-3106 | Block merging of pull requests until they have a successful branch build in bamboo
| STASH-2918 | As a reviewer, I want my pull request approval withdrawn when new commits are pushed to a pull request
| STASH-2521 | Add commit hooks
| STASH-3087 | Include a link to driver changes for SQL Server in the upgrade guide
| STASH-2673 | Show server SSH fingerprint in UI
| STASH-3088 | Add a note about running stash with a dedicated user on *nix platform to the installation docs
| STASH-3081 | Create documentation for changing port number
| STASH-3162 | Pull Request REST resource returns only pull requests in an OPEN state
| STASH-3133 | Stash 2.1.2 failing with MySQL 5.6 due to "specified key was too long" error
| STASH-3034 | Merge Conflict Warning for Lack of Merge Rights
| STASH-2900 | Commit hook permissions not set up correctly when starting stash from AMPS
Authenticate to retrieve your issues

12 issues

## Attachments:

STASH22_PR_approvers.png (image/png)
STASH22_repo_hooks.png (image/png)
STASH22_PR_approvers.png (image/png)
Stash22_repos_hooks.png (image/png)
Stash22_PR_merge_checks.png (image/png)