feat: add navigation over Dockerfile-based projects #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds navigation over Dockerfile-based projects. As of release
0.3.X
and later we use custom function to filter relevant project paths from the all existing Git repository paths. We pass a custom function todirectory.Collect()
as a parameterHow to use?
Execute
echo "mode: dockerfile" > .travelgrunt.yml
in the root of a Dockerfile [mono]repo and then read this chapter.The purpose of this PR is to demonstrate - how [easy] is to add a new working mode to
travelgrunt
- will it be our Dockerfile, Golang source files, Makefile, files with some custom content/comments or any other beasts you spot in typical wild [mono]repo, where directory tree depth and number of subfolders is way to big to justcd
productivelly.#fatigue
We can also think about "true" monorepos with very complex structures and implement more YAML-driven configs like:
Latter is for the future releases, of course, just thinking loudly here 😇