We currently use Subversion & FishEye + Crucible, however my team is looking at moving to Git and possibly Atlassian Stash.
There is a lot more functionality and possibilities with Git which will add complication that Stash seems to help with including workflow support and enforcing best practices.
My question is, how does having Stash manage Git impact users of Git clients? Does Stash enforce security, workflow functionality, etc outside of it's interface? I want to make sure that users can still use their Git clients and enjoy the security and workflow functionality regardless of the interface used.
We definitely enforce the security at the service layer, and the client should never be able to bypass that in any way.
Workflow is a little harder. For example we have a handy feature for automerging release branches, which is currently only triggered when merging a pull request (although technically that can happen if you push a merge for a PR that is already open).
We also have Stash specific integration in SourceTree which enables to interact with Stash without having to go to the web UI.
But in summary - no you shouldn't have to worry about using a particular client. :)
Does Stash enforce security, workflow functionality, etc outside of it's interface?
Why would it want to manage it outside its scope? The answer is your users can use whatever client they want to use to interact with Stash.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs