Atlassian adds workflows to Stash 2.4
Atlassian's Stash, the company's "behind-the-firewall" Git system for Enterprises, has been updated to version 2.4, adding a workflow system to allow companies to better replicate the open source techniques that have helped establish Git as a mainstay of current development practices. This means that developers can now, for example, fork their workflow, creating a Git clone of a repository and isolating their changes from the main workflow, and then merge the changes back into the main code base through Git pull requests.
The process, in Stash, is supported by a collaborative infrastructure that allows interested developers to discuss the fork and merge, and should simplify experimentation with the code base. One use for Stash forking is that it allows developers to contribute code to a code base for which they do not have write/commit access; they can fork and request changes be pulled into the main repository by those who do have commit access. To create a fork, a user needs only click "Fork" in the web front end.
Other additions in Stash 2.4 include support for developers' personal repositories and repository permissions to control read or commit access. Smaller changes include a simple way to manage Stash accounts and the addition of a whitespace query parameter which allows whitespace changes to be ignored when diffing code. Atlassian has also given notice that when Stash 3.0 arrives later this year it will only work with Java 7.0 and later, dropping support for Java 6.0.