Safely ignore files not needed in your repository
The .dvignore
file is used by Diversion to specify files and directories that should be ignored when tracking changes. This helps keep the repository clean by excluding unnecessary or automatically generated files, such as build artifacts, temporary files, and cached data.
Using a .dvignore
file ensures that only relevant files are committed to the repository. This helps:
The .dvignore
file consists of patterns defining which files or directories to exclude. It typically follows these rules:
#
serves as a comment. Put a backslash \
in front of the first hash for patterns that begin with a hash.(*)
match multiple characters./
ignore all contents inside.(!)
explicitly include files that might otherwise be ignored.For game engine-specific projects, .dvignore
ignores:
You can modify the .dvignore
file based on your project needs. If you work with additional tools or frameworks, consider adding their cache or temporary directories to improve repository management.
For example, if you use a custom build system, you might add:
IMPORTANT NOTE: Files and directories that are already committed, will NOT be ignored by .dvignore.
Safely ignore files not needed in your repository
The .dvignore
file is used by Diversion to specify files and directories that should be ignored when tracking changes. This helps keep the repository clean by excluding unnecessary or automatically generated files, such as build artifacts, temporary files, and cached data.
Using a .dvignore
file ensures that only relevant files are committed to the repository. This helps:
The .dvignore
file consists of patterns defining which files or directories to exclude. It typically follows these rules:
#
serves as a comment. Put a backslash \
in front of the first hash for patterns that begin with a hash.(*)
match multiple characters./
ignore all contents inside.(!)
explicitly include files that might otherwise be ignored.For game engine-specific projects, .dvignore
ignores:
You can modify the .dvignore
file based on your project needs. If you work with additional tools or frameworks, consider adding their cache or temporary directories to improve repository management.
For example, if you use a custom build system, you might add:
IMPORTANT NOTE: Files and directories that are already committed, will NOT be ignored by .dvignore.