How to ignore files and folders within a mudstack workspace.
.mudignore
file.
To use mudignore, create a text file in the root folder of a workspace and set the name to .mudignore
. The extension for the file is .mudignore
and the name is empty.
If there is no .mudignore
file, we will return to the default list of files to ignore.
By default, here is what we ignore:
“folder name/file name.txt”
!
includes what should be excluded. If there is a rule *.txt
, !item.txt
will include any .txt files with the name “item”.
/
is a separator for directories.
Leading separators like /item
searches for “item” from the root folder. The results include both files and folders.
Separators after a term like item/
searches for a folder “item”.
Build a folder path with separators like /folder1/folder2/file
.
*
matches every character except /
.
?
matches one character except /
.
Range notation [a-zA-Z]
will match one of the characters in a name.
/**
matches everything inside a folder like folder/**
.
**/
matches zero or more directories. a/**/b
matches a/b
, a/x/b
, a/x/y/b
and so on.
Additional *
are considered regular asterisks and will match according to the previous rules.
.mudignore
works exactly like other files when you push or pull changes. It has it’s own version history, so all version actions are available to you.
What happens to ignored files once they are in the cloud?
What happens to files that get ignored locally?
What happens to files that are not ignored locally?
What are the differences between mudignore and gitignore?
.mudstack
folder will always be ignored, regardless of whether you remove this rule from your .mudignore
file.