Regarding parallel release

[Shailesh Phatak]

I want to maintain parallel release and want to make sure that if anything is committed to once branch gets automatically committed to another. Is it possible ? in this way I will make sure that nothing gets missed from both the branch. Consider below scenario

v1.0 <- Master

v2.0 <- v1.0

If developer commit anything in v1.0 then I need this to be updated in v2.0. I know this is bit risky but do we have any provision in bitbucket to tackle this scenario ? OR would you like to suggest any other good approach ? My main issue is I do not want multiple commits to two different branches so that developer do not miss anything to commit into another branch.

[Ana Retamal]

Hi Shaileshs,

Have you considered using webhooks or Bitbucket Pipelines? Would any of these suit your needs?

Kind regards,

Ana