This old post has a (somewhat messy, mixing glob **/Assets and specific /Assets paths) ignore.conf example:
However, it also contains /ignore.conf - what gives? How would this actually ever be committed if the file itself is ignored?
(more bewilderingly, it still shows up in my changed items)
I also want to use plastic for a larger monorepo, so it would contain a solution in the root, and many sub-projects (some nodejs, some ASP.NET, and one or two unity projects in sub-folders)
Can I have sub-confs like in .gitignore?
Hi, ignore.conf is a local configuration file, so each developer can have their own ignore.conf rules. If you want, you can commit the “ignore.conf” to the repo, but by default is a local file so it should be added to the “ignore.conf”.
Plastic SCM also supports global configuration to be distributed between all the clients: Plastic SCM version control · Administrator's guide
You can also commit the “ignore.conf” if it fits your needs, and users won’t have to define their own customer ignore rules. But it’s not the default behavior.
In the following link, we explain the different rules you can define in the “ignore.conf”:
Please let us know if it helps.
Users can define their own rules in their global conf, we absolutely don’t want anyone on the team second-guessing if any of the 100 file types your average project tree has should be included or not.
Thanks for the answer!