Using environment deployment variables

[Michael]

We have a BitBucket Project with a repository which contains variable files which are populated by the application developers (who can use this code to deploy to Dev/SIT). Our problem is – how can we separate this code from the Operations guys (who can deploy to production)

Is there a way to e.g. have the application developers have permissions to the develop branch, but the operations team have permissions to the master branch – which is merged post SIT deployments? Is that possible?

Or, do we have two separate repositories (and potentially projects) - and the operations team would clone the application developers repo and update the code as required. Is that the typical method?

Anything you can provide to steer us in the right direction would be appreciated.

Thanks

 Michael

[Anton Shaleev · Accepted solution]

Hi Michael

The second way will work for you as I understand, but instead of two repositories, you can fork the current repository.

In that case, your developers will be able to create PR's to merge changes into the master of forked repository while all the branches of the original repository.

Kind Regards

Anton