We have a Drone pipeline with a specific step which uses image docker:git to merge code from one branch to a target branch.
In Bitbucket settings > Branch restrictions: we gave to the user who triggers the pipeline write access to the target branch in where we want to merge the code.
The step to merge code exited with code 1.
We noticed that the step is successfully completed only if we add the user who originally activated the repository.
So, supposed that the user who triggers the pipeline is a Drone admin user with admin privileges to the repository and write access to the target branch, the pipeline step to merge code will exit with code 1.
If we give write access (on target branch) also to the user who activated the repository, then the step is successful.
Finally, we tried to disable the repository. Then, the user who triggers the pipeline activates again the repository. We gave the user write access to the target branch and the step exited successfully with code 0.
Why is that?