Hi, just wanted to clarify a feature of automatic fork syncing.
If I have an upstream with branches master and dev
and have a fork of upstream called origin with branches master, dev and feature and it also has fork synchronization enabled,
does this mean that only origin/master and origin/dev will be synced, and origin/feature will not be synced because upstream does not have a branch called feature?
Reading the Atlassian Bitbucket article "Keeping forks synchronized" did not make this very clear to me. Thanks!
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