project.garden.ymlfor clarity, but you can also use
garden.ymlor any filename ending with
modules.excludefields in project configuration files.
modules.excludefields are a simple way to explicitly specify which directories should be scanned for modules. They both accept a list of POSIX-style paths or globs. For example:
modulesdirectory, but exclude the
include, only those patterns are included. If you then specify one or more
excludepatterns, those are filtered out of the ones matched by
include. If you only specify
exclude, those patterns will be filtered out of all paths in the project directory.
modules.excludefield is also used to limit the number of files and directories Garden watches for changes while running. Use that if you have a large number of files/directories in your project that you do not need to watch, or if you are seeing excessive CPU/RAM usage. The
modules.includefield has no effect on which paths Garden watches for changes.
.gardenignorefiles and excludes any patterns matched in those files. You can place the ignore files anywhere in your repository, much like
.gitignorefiles, and they will follow the same semantics.
.gardenignorefile in your project root directory:
publicdirectories across your project/repo, and all
modules.includefields in your project config, and
includefields in your module configs. If a path is matched by one of the ignore files, the path will not be included in your project or modules.
dotIgnoreFilesfield in your project configuration. For example, you might choose to also respect
.gitignorefiles (this was the default behavior prior to Garden 0.12.0):