Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I did this:
# drush dog-init --upstream=drupal-6.20 --collab=file:///tmp/sansbark sandbox6
But no repo is cloned to /tmp/sansbark
sandbox6/.git/config:
# cat config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "upstream"]
fetch = +refs/heads/*:refs/remotes/upstream/*
url = git://git.drupal.org/project/drupal.git
[branch "master"]
remote = collab
merge = refs/heads/7.x
[remote "collab"]
url = file:///tmp/sansbark
fetch = +refs/heads/*:refs/remotes/collab/*
Comments
Comment #1
sdboyer CreditAttribution: sdboyer commentedYep - collab indicates where pushes are made to, not where the initial clone is made from. Initial clone comes from 'upstream,' then your work goes on in collab. Two separate remotes.
We need to fix the docs so that this is clearer.
Comment #2
Island Usurper CreditAttribution: Island Usurper commentedHowever, if the collab repo doesn't exist, and it's supposed to be on the local filesystem, it might be a good idea to create it automatically.
Comment #3
sdboyer CreditAttribution: sdboyer commentedYeah, I can see that making sense. I'm trying to drive towards just the really necessary stuff initially, though, so recategorizing this as a feature request. I know it's a small thing, but I'd have to come up with a way of figuring out if the provided collab target is a local filesystem path, and that feels like a struggle right now. Soooo...I'd be happy to accept a patch :)