When I Add a subtree it all works great locally. However it seems all the subree information is lost when it hits bitbucket, so a team member who clones the repository doesn't see the subtree info.
so I have :-
Then I clone that somewhere else
So if a team member changes something in project "LetterA" they don't have it setup so they can push their change to the lib repository.
As far as I can tell, the only reason why sourcetree knows of subtrees is because it records in "sourcetreeconfig" that there are some. But how do you share this with a whole team ?
submodules caused all kinds of grief when branching and merging and just feel clunky
However, I've abandoned subtrees now... and gone with subrepos
It solves the problem really nicely ( though it is all command line, but pretty straight forward )
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