Steps to reproduce
1. Create branch locally and checkout that branch.
2. Modify/add/remove files and commit the changes
3. Push the local branch to origin
4. Create pull request
5. Modify more files, do commit
6. Push the updated branch to origin.
The workaround is to decline pull request and open it once again.
This issue concerns only one repository and there no special hooks defined for it.
We use Bitbucket 4.0.1 (DataCenter). Restarting the BitBucket doesn't help.
When we clone repo as a bare like below:
git clone --mirror <URL> and later push to the just created:
git push --mirror <URL>
the issue doesn't exist, everything is fine there.
Can you open a support request for this problem at https://support.atlassian.com, reproduce the problem and include a support zip (Administration > Support Tools) that includes the logs? That will allow us to further investigate the problem.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot