My company has a self-hosted Bitbucket setup. We would like to have developers work in their own forks for added safety and to keep branches in the main repo under control. However, git operations on a forked repo are roughly an order of magnitude slower, making this a poor option.
For example, I have copies of both the main repo and a synced fork on my machine. With both repos in the same state and already up to date, a simple `git fetch` takes 5 seconds on the base repo and 37-61 on the fork.
Why is this, and is there any way we can improve the situation?
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