How to auto merge or auto deploy in Stash like in Bitbucket?

[Shawn Whitaker]

In Bitbucket we were able to auto deploy and in Stash we're not able to figure it out and would like some help. We have already search on and this didn't work https://answers.atlassian.com/questions/11982126 

[Adam]

Yeah that looks like a great place to start! Webhooks are definitely the way to go. The only built-in way Stash communicates with clients is through the standard Git client, so there's no other kind of "hook" available for you to listen to.

[Rafal Radolinski]

@Adam Ahmed by auto-deploy we basically mean that our staging website is being updated every time we run "git push". We are currently only using a master branch. Each developer works on his own clone of the same repository and our staging website codebase is a clone as well. Is there a way to add a hook to that particular clone that would trigger "pull" or "checkout" action, or do we need to create a webhook? Is this a good place to start if we are about to use webhooks? https://confluence.atlassian.com/display/STASH/POST+service+webhook+for+Stash?continue=https%3A%2F%2Fconfluence.atlassian.com%2Fdisplay%2FSTASH%2FPOST%2Bservice%2Bwebhook%2Bfor%2BStash&application=cac

[Adam]

I suppose what would actually help is clarity around "master" vs "develop" versus whatever branch you use for "currently deployed", "upcoming deployment" and for "previous deployments" if any.

[Adam]

Can you explain what you mean by "auto deploy"? Stash only hosts your code. At best, you could use a webhook to tell a separate web application to deploy when some event occurs in your codebase. Automerge is also meant to "flow downhill" from older releases toward the newest release and then your development branch. It would be good to understand how you have your branches set up that you would need to merge all changes from master into a different branch. What does "master" mean to you, vs "develop"?