What's New In Stash 2.0

Powered by Git. Controlled by You.

By enabling developers to create, merge and delete branches at will, using Git can feel like living in the Wild West, especially for tech leads and release engineers. Stash's big new feature, Branch Permissions, puts the reins back in your hands so you can control the chaos a little (or a lot).

Imagine all the flexibility of Git with the control needed in the Enterprise. That's Stash 2.0.

What's New in Confluence 4.3 Team Collaboration Software

Per-branch Permissions

Some development workflows require that specific developers oversee merges into the master or release branches, while other developers work on bug-fix and feature branches. Branch Permissions let you turn this "gentlemen's agreement" into a seamless, enforceable process, reducing confusion and time wasted backing out changes that were merged in prematurely.

  • Contractors: restrict external developers to certain branches to easily review commits before integration in production code
  • 'Blessed' branches: new and junior team members can be granted access to release and deploy branches as soon as they're up to speed
  • Avoid accidental pushes: newbies who are still learning the complexity of Git can avoid the "oh s—" moment

Enhanced Pull Requests

Branch Permissions let you select a "gatekeeper", typically a senior developer, who is responsible for ensuring that all the code going into production has been properly tested and reviewed. No matter what the experience of your other developers and any externally developed code, everything is vetted before it's integrated into your product. Stable and high quality code for the win! By giving access to critical branches only to the gatekeepers, all other developers can use pull requests to notify the gatekeepers of new changes. These gatekeepers are then responsible for reviewing, if and when, the code is ready to be merged to the stable branch.

@mentions

Pull requests and comments bring code discussions into Stash. With @mentions, casually bring members of your team into any code discussion. Simply type in  “@” + user name as part of a comment and they will receive a notification that they have been mentioned as part of a pull request conversation. From there, the discussion continues inside of Stash and is available for everyone to view.

Loop the right people into the conversation, at the right time. Want input from a Product Manager or Architect who isn't a reviewer on the pull request? @mention them so they can lend their expertise. It's a non-intrusive way to widen the discussion on specific threads of conversation.

Markdown Support

Providing context and emphasizing key points are important when having written discussions around your code. Stash now gives you a boost with support for markdown in comments and descriptions. Bring your words to life and get your point across quickly.

  • Emphasize parts of your comment or create lists to bring your points across
  • Share links to requirements and issues related to the feature you are implementing
  • Provide code examples, formatted just like in your IDE
  • Include screenshots into the discussion for any UI focused features

Have a look around Stash 2.0

  • Pull Requests and Branch Permissions|
  • Mentions|
  • Markdown|

Latest Stash blog

Steve Smith

Practical continuous deployment

In February, I had the pleasure of speaking with the London Atlassian User Group (AUG) about some of our experiences with continuous delivery and deployment at Atlassian. The slides for this are avai ...

Read more on the Stash Blog