nextcloud / nextcloud/desktop

Overriding sync-exclude.lst in subfolder

Open
#5,331 0 comments 0 reactions 0 assignees View on GitHub
feature: :arrows_counterclockwise: sync engine
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 17h
Merged PRs (30d)
123

Description

### How to use GitHub

* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you want to have the same feature implemented.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.

### Feature description
We have a repository where ``.cmo`` files are not synced because they are generated by an OCaml compiler and tied to the compiler version, which may differ from computer to computer.

However, for a specific project where we generate ``.cmo`` files for fixed versions of the OCaml version (for distribution to students), I would like ``.cmo`` files in that specific subfolder and its subfolders to be synced.

I put an empty ``.sync-exclude.lst`` in that subfolder in the hope that it would take precedence over the one a the repository root, but that does not seem to be the case. I also cannot find in the documentation a way to expressly un-exclude some patterns (which would work because the files to sync are all called ``support.cmo``).

I propose either :

- ``.sync-exclude.lst`` in subfolder taking precedence over those in folders above (even when empty), or
- a syntactic device for an exclusion pattern in a ``.sync-exclude.lst`` to not cover some cases (ie. exclude ``.cmo`` files that are not ``support.cmo``, or exclude ``.cmo`` files that are not ``some/path/*.cmo``).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.