Closed jacebrowning closed 5 months ago
@jacebrowning This was removing any configs that come in from any pulled dependencies but still allowed subdirectories to be included for aggregating configs. I would not remove it. What is the behavioral difference you are observing?
@DavidWatkins I opened https://github.com/jacebrowning/gitman/issues/337 to show how to reproduce the behavioral difference.
@jacebrowning Ah I see. It's been a year and I cannot remember exactly why I wanted recursion over directories without automatically cloning those sub-dependency gitman.yml
files, but with fresh eyes, it makes more sense to allow for this behavior. Go ahead and push this change and we'll make changes on our end to support the new workflow if it breaks anything.
@DavidWatkins thanks for taking a look! I'll release this as 3.5.2
and please open an issue if you notice any strange behavior.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 91.07%. Comparing base (
16cfe3c
) to head (d1c1917
). Report is 17 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Fixes #337
@DavidWatkins can you remind me the purpose of the function I removed in this pull request? As far as I can tell the alpha release from this branch is behaving as I expect in relation to nested configs but
main
is not.