mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #563] Add a button to the main page that syncs all accounts at once #394
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#394
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 @Tank-Missile on GitHub (Jun 10, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/563
For users such as I that use more than one account, it would save me a few clicks having one button that synced all of my accounts at once.
@marcelklehr commented on GitHub (Jan 30, 2021):
Mh. The automatic sync interval should take care of syncing all accounts. Why would you want to force sync all accounts at once?
@Tank-Missile commented on GitHub (Jan 30, 2021):
In case I wanted to sync all accounts at once before the next interval. If I made a lot of changes to my bookmarks at once, I want to make sure they get backed up immediately. Floccus has some lingering issues where if a lot of bookmarks and folders get rearranged/added/deleted, something is bound to go wrong and screw up my bookmarks. I've been having trouble trying to recreate the issues. Maybe they were fixed at some point.
@github-actions[bot] commented on GitHub (Dec 8, 2024):
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.