Ignore Rules

Overview

Ignore rules define which files and folders the Workspace should skip. They keep temporary or generated files out of changelists.

Rules are stored in .kscmignore at the root of each repository. In a workspace with multiple repository links, the Ignore Rules tab shows rules for the repository of the currently selected folder or file.

At the top of the tab, Workspace shows the current repository and the .kscmignore file being displayed.

Ignore rules from one repository do not apply to other repository links.

When you modify rules from this tab, Workspace automatically attempts to mark .kscmignore for add or edit in the currently selected repository. You can submit .kscmignore like any other file, preserving history and making rule changes easy to share.

When you use it

Use this tab to manage and filter what should be revisioned on the server, such as excluding build outputs or caches. This area is mainly for advanced users. Teams usually define these rules early in a project and update them only occasionally.

What you can do here

• Add, edit, or remove ignore patterns
• Review which rules are active
• Browse multiple rule sets, each bound to a directory in the current repository
• In each rule set, define rules explicitly, by name, or by extension
• Use the Exceptions tab to keep specific files or subdirectories included when broader rules ignore a parent directory
• Keep change lists focused on real work

Typical flow

1. Select a folder or file so the correct repository link is in context.
2. Open Ignore rules and confirm the repository and .kscmignore shown at the top.
3. Update rules or exceptions in the relevant directory rule set.
4. Reconcile to confirm files are excluded as expected.