Acren Posted January 10 Report Share Posted January 10 Hi there. We've started trying out xlinks to manage our component repos, and it seems to work well apart from one thing: The branches on the parent repo getting created on the child repo is really undesirable from our point of view, because these branches only make sense in the context of the parent repo and mean nothing to the child, they are also all just empty merges and don't contain anything meaningful. So we also get all of these automatically created empty branches cluttering the child repo and creating triggers and notifications where we don't want them to, and I can only see this getting much worse when there are more xlinks as well. Can we disable the auto expansion and keep the xlink writable? The desired behavior would be to always use the /main branch on the child and not create other branches. Essentially this would be the same thing as having an expansion rule for every branch on the parent repo mapped to /main on the child repo, but I'm not sure how to specify this, maybe I'm missing something because I'm still new to xlinks. Thanks! Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now