Use a file to ignore / exclude files or folder
Add functionality similar to a gitIgnore file or nomedia files. Allow a user to add a .ignore file to exclude local files or folders from being synced.
Example: I have NodeJS projects on my OneDrive but get sync errors because the file path is too long. The long paths are primarily extra modules that do not need to be synced. It would be nice to be able to exclude certain folders or files.
Hi, for this scenario we’d recommend putting the files outside of the OneDrive folder. The design is that all files in the OneDrive folder will be sync’d and files outside the folder will not be sync’d.
Jakub Zawierucha commented
Angus Logan, Your design guide lines are wrong - there are and there will be always files that are temporary or just "junk" produced as a output of "bigger process". You must understand, that OneDrive or simlar tools are not just "sync one folder in cloud toy". We - users work here hard and we need pro tool.
Please reconsider again putting this requirement into project.
Keith Pickering commented
Does Microsoft think developers just don't use their products. Fix OneDrive already, guys.
Cannot understand the decline. Having a nodejs project for college in my OneDrive - local node packages blow up the OneDrive Synch almost instantly. Why not just ignore everything that would be ignored by the .gitignore file anyway? Quite explicit, don't you think?
Juan Jose Mendoza Santana commented
I thinks this is a desirable feature. Specially for developers, but also for commons users. It would be really really nice to have it.
Moritz Schubotz commented
Yeah but think about it, with OneDrive on 5 of my PC's it would be nice to add an Ignore for ONE OF THEM...This way my WORK Virus detection doesn't go off yet i get access everywhere else!!! Smart feature if you can ignore certain clients...
Oldřich Dlouhý commented
This is a must for developers syncing projects between table PC and mobile PC.
I would strongly suggest you reconsider your design.
Raul Sandrea commented
I'm on exactly the same scenario as Victor, I have to install grunt inside the project folder and once I do that OneDrive stop syncing because of the file path being too long.
This would be a mejor feature for OneDrive
I agree with Kenneth...it's must feature for developers! I can't believe that you declined this feature!!
Kenneth Tran commented
Agreed that it's a must have feature for developers. I want to use OneDrive for syncing code but don't want the binaries, test files, and other temporary files to be synced.
Chris Vann commented
I can't believe someone at Microsoft thought it was OK to simply decline this feature request as a conflict of design / intent. It's clearly driven by a very valid use case and it shouldn't be that hard to implement. Exactly how far up there is your head stuck?
Christoph Rüegg commented
I second what Noel Abrahams said - there are a lot of use cases where there is a scratch-style subdirectory that you don't want to sync and you also have no control over its location. This is not just VisualStudio, but e.g. also Lightroom where you may not want to sync the preview cache.
Noel Abrahams commented
@AngusLogan, I don't think you've understood the use-case here. This enables scenarios such as using OneDrive to build a Visual Studio project. Clearly we would like to exclude build artefacts and external libraries. How does one "put the files outside of the OneDrive folder" for this case?
There is kind of a workaround which kind-of approximates this feature request. It would benefit from (a) being kept around as-is (there are many ways to break it, I could see) and (b) getting a slight UI improvement.
The workaround is this:
1. Sync the whole folder (let it finish).
2. Right click on OneDrive in file explorer and go to "Choose Onedrive folders to sync".
3. Uncheck the folders you don't want synced.
Warning: this will delete those folders in step 3, but presumably these are files that can easily be re-created (so don't use this for files that are just too big, like giant video files).
There are a few down-sides to this very useful feature which could stand some improvement:
1. Basically, this works because OneDrive views this as a conflict (i.e., an error). So, the entire folder tree all the way up will have a red 'x' icon to indicate that there was a "problem" synching. So, you can't get a quick overview of sync status (i.e., in progress [arrow circle] or completed [green checkmark]). This seems easily remediable: if the folder is unchecked, then "duplicate" folder names are not errors, so don't show a red 'x'.
2. Folders that are unchecked for sync should not be deleted. Just leave them there.
3. Allow us to uncheck folders for syncing even before the sync is complete. Currently, you have to wait until everything is uploaded before it will allow you to do this. (Annoyingly, you can go through the whole process of specifying which folders OneDrive should skip, then it will tell you you can't do it once you hit Apply.) If the folders are large, this can really take a long time. Yes, if you think about it, you can fake it by moving stuff around manually, but that is very error prone and cumbersome.
So, the feature is kind of there already. It just needs to stay mostly the way it is, and it could use a few improvements.
Petah Piper commented
Ken Rimple commented
This would be a really fantastic feature. Highly suggest Microsoft implements it. The abomination of the OS path limit -vs- the filesystem allowing longer filenames makes this tough, and having ephemeral files locally generated but not synced would be a big help.
I'd like to exclude folders, but for a much different reason. I write software and each time I compile, the compiler creates ~600 temporary files. OneCloud then attempts to upload these "changed" files. I compile about every 10 minutes, so OneCloud is continuously uploading (and slowing down my computer).
I would love this functionality. I'm using onedrive for my prj, so when I build an app all output files from target folder want to be sync which is useless - I would like to exclude them.
must have feature... really need it.