StoneSVN

STONESVN · PRACTICAL GUIDES

Ignore logs and generated files across SVN working copies

By the StoneSVN project · Checked against StoneSVN v1.1.2 · Reviewed

StoneSVN lets you configure one set of local file filters for all working copies. Use this when logs, generated files or dependency folders repeatedly clutter your review. The filters belong to StoneSVN; they do not change SVN repository properties.

How do I enable global file filters?

  1. Open Settings → File Filters.
  2. Enable filtering and enter one pattern per line.
  3. Return to a working copy and refresh the list.
  4. Check that the intended files are hidden and that files you need to commit remain visible.

Example patterns

.DS_Store
*.log
**/node_modules

.DS_Store matches that filename at any depth. *.log matches log filenames. **/node_modules matches dependency directories and their contents. Use patterns that fit your repository; a log file can be intentional project data.

How do the wildcards work?

* does not cross a directory separator, ? matches one character, and ** can cross directories. Names without a slash can match at any depth. Patterns containing a slash are relative to each working-copy root. Negation with ! is not supported.

Is this the same as svn:ignore or svn:global-ignores?

No. StoneSVN applies its own filters locally. It does not write svn:ignore or svn:global-ignores, and other SVN tools will not inherit these settings. If your team needs shared repository rules, manage the appropriate SVN properties and commit those property changes separately.

A pattern naming .gitignore hides that file itself; it does not import Git ignore rules from its contents.

What happens when I add or commit files?

StoneSVN checks the selected scope when adding files or committing. If a recursively added directory includes filtered items, add the intended files individually or adjust the filters. Filtering does not remove a file from version control, delete it from disk or undo a previous commit.

Download official installers · Source at v1.1.2 · Report an issue