Jace Browning
Jace Browning
This could be accomplished by first checking out the `rev` and **then** the locked `rev`.
- [x] Wait for https://github.com/jacebrowning/gdm/issues/80
@brandonaut Yeah, I think that could work. It would be good to see a proof-of-concept PR for that to see how much has to change.
> It doesn't feel too natural that updating `sparse_paths` and then re-running install or update doesn't pull in the new paths defined. I agree and would be open to a...
Do you have a use case for circular dependencies?
Yeah, I'm just trying to understand how common this situation is to warrant a feature to prevent it. 😄
Thanks for the report! > if my tf-module contains a gitman.yml By this do you mean that `git@githost:tf-module.git` has its own set of dependencies to be recursively managed by `gitman`?...
Does `gitman-subsub.git` have it's own `gitman` config file? Can you share that as well?
Thanks, that's helpful! You're correct that groups are only processed once at the top level, so I believe this issue is a request to pass that information to each nested...
This is the spot where `"production"` is translated to `["tf-module-production"]`: https://github.com/jacebrowning/gitman/blob/5acc0e4b1d5c15683213563901acd0349a1fa155/gitman/models/config.py#L87 This is the spot where we recurse into nested repositories: https://github.com/jacebrowning/gitman/blob/5acc0e4b1d5c15683213563901acd0349a1fa155/gitman/models/config.py#L117 You'll notice that `names` are not forwarded to...