mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #576] Option to exclude folders from sync #403
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#403
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DerDanilo on GitHub (Jun 18, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/576
Is your feature request related to a problem? Please describe.
When syncing the root folder to my personal server it works all fine. But as soon as one also activates additional subfolders to be synced to different other servers it can become quiet messy when not taking care of selecting the right folder.
Describe the solution you'd like
Describe alternatives you've considered
None currently, it's quiet messy.
Additional context
Please write me if this is required.
@marcelklehr commented on GitHub (Jun 18, 2020):
This used to be default, and I think I'll change this to be the default again. Still, I agree that an option would be good.
@DerDanilo commented on GitHub (Jun 18, 2020):
The problem is also that the root folder sync will sync all bookmarks if none are excluded, which will then sync those bookmarks to within other browser who are not supposed to have "subfolder bookmarks" (addtional sync accounts).
@marcelklehr commented on GitHub (Jun 18, 2020):
Fixed by reverting the original switch to include nested account by default. Will need to develop an option.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.