The Plastic equivalent of .gitignore is ignore.conf
Posted by jpluimers on 2018/07/26
A while ago, I landed a place using Plastic SCM, so I had to adopt some idiom from the git world.
The [WayBack] .gitignore equivalent in Pastic SCM is ignore.conf. Here are some links to documentation on it:
- [WayBack] Where can I find documentation on how to use ignore.conf? – General – Plastic SCM Community
- [WayBack] Plastic SCM blog: Configuring ignored items on your workspace
- [WayBack] Plastic SCM version control · Administrator’s guide: Global file configuration
- [WayBack] Plastic SCM version control · GUI guide: Commands for Private Objects
There is another file with a similar, but deceptively different name and behaviour: hidden_changes.conf. There ignore.conf ignores changes, hidden_changes.conf completely hides them. I am still not sure what subtleties are involved in the difference between “ignore” and “hide”, as the documentation is confusing and hidden_changes.conf can also appear in the root of a repository:
ignore.confContains the paths of the private files to be ignored in the Pending changes view. The ignored files are files that you have no intention of placing under source control. This config file is placed at the root directory of the workspace, or in the plastic-global-config repository so that all clients have the same settings by default.
Learn about how to configure the ignored list.
These configuration files are supported:
Important: These are the files that can be globally configured:
branchexplorer.confcloaked.confexternaltools.conffiletypes.confhidden_changes.confignore.confreadonly.confserveralias.conf– This file can only be placed in the/allreposdirectory (no other location is supported for this configuration file). The Plastic SCM GUI will load the aliases during the startup.writable.conf
So I based mine on Tortoise SVN Global Ignore Pattern for Delphi and Visual Studio containing at least these:
*.identcache
*.local
*.dcu
*.rsm
*.bak
*.~*
*.tvsconfig
__history
__recovery
ModelSupport_*
–jeroen






Leave a comment