OneDrive


Feedback by UserVoice

I suggest you ...

Make it possible to ignore build artifacts

When using OneDrive as a location development projects (e.g. Visual Studio Projects, nodejs, ...) the folder contains a lot of build artifacts which shouldn't be uploaded to OneDrive. Those files can't be put outside of the OneDrive folder because the development tools expect them to be there. This causes unnecessary load and other problems (e.g. long file paths) for the local machine and the OneDrive service.

OneDrive should be configurable at the folder level to include/exclude certain files. Configuration could be done in a '.onedrive' file for example and work recursively in the folder tree (like gitignore).

The .onedrive file could be used to configure other features as well.

140 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Tom Deseyn shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
not right now  ·  Douglas Pearce responded  · 

We like the suggestion and the approach with the .onedrive file. But we want to be transparent that we aren’t likely to get to this in the near future.

12 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

OneDrive Archive: General

Feedback and Knowledge Base