Actually it's already implemented. When you navigate to the enlistements of a project, you can exclude directories there.
First of all, thank you for this solution. It works really well for me. I've got just two hints:
Make the textarea wider. In SallyCMS the list is really ugly because of the long filenames: https://www.ohloh.net/p/sallycms/enlistments/237816/edit There is enough space left, so use it!
Allow more than 1000 characters. Since no wildcards are allowed, I had to specify all jqueryUI files on their own and even let the last disallow line out, because Ohloh rejected it.
Having ant-like wildcards would be really great. I have Maven Java projects that keep generated code in specially-named packages but consist of multiple maven modules. With a pattern, those would be easy to match and little pain to maintain - but without... lots of work :(
There are cases when it would be helpful to have an inclusion list rather than an exclusion list (you could select which end to start on). These are cases when a single, monolithic repository (in this case git) is being used for multiple projects. An inclusion filter lets the project focus on the paths it uses without having to worry about what anyone else is doing.
Any chance for an option to make the list opt-in rather than opt-out?
couldn't you just have multiple enlistments in those cases?
This is a great feature. However, I also hit the 1000 character limitation, since I want to include several files distributed over several directories. It would be great if you could relax this limitation. Thank you!