-
Notifications
You must be signed in to change notification settings - Fork 148
"clone" mode for gb-vendor #316
Comments
All the logic is there in the manifest format to implement this. It's on On Fri, 21 Aug 2015 22:55 Victor Starodub notifications@github.com wrote:
|
Sure, I'll give it a try. |
The trick is to use the prefix field of the manifest to strip out the import path prefix that TV projects have.
|
@davecheney Hey! I am back (after a looong time)! I can implement this, but I didn't quite get the "prefix" that you are talking about Dave. |
It would be convenient to be able to optionally clone vendored paths as proper repositories.
Use scenario:
I've got project repo and a shared repo. I'm developing a feature in the project repo and need to add some supporting code to the shared repo. I want able to write/test/commit the supporting code inside the "vendor/" dir.
Currently with gb, it looks like I've got following options:
I suggest adding something like '-clone' option for 'gb-vendor fetch', that would get registered in the manifest. The repository would simply get cloned. In case of an update, simply failing if the vendored repository is not clean seems ok.
Since gb-vendor is already doing the job of cloning a repo and branch tracking, it might be quite easy to implement.
The text was updated successfully, but these errors were encountered: