In most software projects there are lots of generated/temp files, caches etc. (such as files generated during intermediate compilation steps or third party libraries downloaded by package managers like Maven, Composer, Pip) that should not be uploaded anywhere because they can take a lot of space and/or regenerated often, like every time I build/run a program to test it (and sometimes this can even cause some file access conflicts if compiler and InSync try to access/delete files at the same time), and they can be easily regenerated.
So current ignore list works mostly fine, but there are things that can be improved like I mentioned above.
- Separate ignore lists per folder would simplify filters and solve the issue with similar file names like the one I mentioned: in C++ projects *.obj files are generated by compiler and should be ignored while in other folders it can be a 3D model or something else that should not be ignored.
- Backup/import/export: I don’t know where InSync stores ignore list, is it per account or per device? If per device, then it would be very inconvenient to retype all filters if I move to a new PC. And if per device, then export still could be useful to share with other people.
- Also import (or just copying) would be very useful for per folder filters (if you add this of course ) to avoid retyping filters manually for all similar projects.
- Importing per folder filters from .gitignore or just supporting it can be useful (and would probably solve all of the issues for me), but probably not very important, usually there is not that much file types/folders in a project that have to be ignored by InSync and sometimes it can be even useful not to ignore some files from .gitignore in InSync (for example user settings). So maybe a separate file (.insyncignore) would be better
I hope I managed to clarify it, feel free to ask more questions