starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 22:26:06 +03:00

[GH-ISSUE #2000] Floccus "force pushed", deleting my Git history #1336

New issue

Closed

opened 2026-02-25 22:39:43 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:39:43 +03:00

Owner

Originally created by @alexandru on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2000

Which version of floccus are you using?

5.5.6

How many bookmarks do you have, roughly?

IDK

Are you using other means to sync bookmarks in parallel to floccus?

Yes, Firefox with its Mozilla account, Brave's sync, across macOS / Android

Sync method

Git

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

No response

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Yesterday, Floccus force-pushed changes to my GitHub repository, with the activity on that repo now looking like this:

I've only noticed it today because I got a warning that synchronization would delete 64% of my bookmarks:

And now that git history looks like this, with every history log that happened before Jul 22 being deleted, which is terrible, because I wouldn't know what actually got deleted:

I don't remember activating any setting allowing Floccus to wipe my Git history clean via force pushes. At this point the workaround will probably be to protect the main branch from force pushes in GitHub.

Expected Behavior

If I'm using Git, I expect it to never force push without my explicit, unambiguous consent (which was never given).

To Reproduce

I don't know what triggered it to do a git push --force

Debug log provided

I have provided a debug log file

Originally created by @alexandru on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2000 ### Which version of floccus are you using? 5.5.6 ### How many bookmarks do you have, roughly? IDK ### Are you using other means to sync bookmarks in parallel to floccus? Yes, Firefox with its Mozilla account, Brave's sync, across macOS / Android ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. _No response_ ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug Yesterday, Floccus force-pushed changes to my GitHub repository, with the activity on that repo now looking like this: <img width="500" alt="Image" src="https://github.com/user-attachments/assets/bca8dab5-3175-40fa-87a7-4ff41e01daa9" /> I've only noticed it today because I got a warning that synchronization would delete 64% of my bookmarks: <img width="411" height="324" alt="Image" src="https://github.com/user-attachments/assets/586c9582-7dfa-4318-bfab-cb515342a6ab" /> And now that git history looks like this, with every history log that happened before Jul 22 being deleted, which is terrible, because I wouldn't know what actually got deleted: <img width="500" alt="Image" src="https://github.com/user-attachments/assets/59830d7e-57ad-49a0-8c43-60a2a6784eaa" /> I don't remember activating any setting allowing Floccus to wipe my Git history clean via force pushes. At this point the workaround will probably be to protect the `main` branch from force pushes in GitHub. ### Expected Behavior If I'm using Git, I expect it to never force push without my explicit, unambiguous consent (which was never given). ### To Reproduce I don't know what triggered it to do a git push --force ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:39:43 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:39:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 23, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@github-actions[bot] commented on GitHub (Jul 23, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:

kerem commented

2026-02-25 22:39:44 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 23, 2025):

Hello @alexandru
I'm sorry for the trouble this has caused you.

Floccus sometimes force pushes when it thinks it is safe to do, which in this case obviously wasn't the case. I will change this in the next release.

I expect it to never force push without my explicit, unambiguous consent

Good point!

I wouldn't know what actually got deleted

The browser that shows the failsafe error should still have the bookmarks intact.

@marcelklehr commented on GitHub (Jul 23, 2025): Hello @alexandru I'm sorry for the trouble this has caused you. Floccus sometimes force pushes when it thinks it is safe to do, which in this case obviously wasn't the case. I will change this in the next release. > I expect it to never force push without my explicit, unambiguous consent Good point! > I wouldn't know what actually got deleted The browser that shows the failsafe error should still have the bookmarks intact.

kerem commented

2026-02-25 22:39:44 +03:00

Author

Owner

@alexandru commented on GitHub (Jul 23, 2025):

@marcelklehr I recovered them, no worries.

I'm using multiple browsers, yesterday I've set up a new Vivaldi instance and this is probably what's caused it — especially since I definitely have 2 ore more browsers syncing concurrently.

Git's history is what gives me peace of mind that in the worst case (e.g., bookmarks get deleted without my knowledge), I can still recover them due to having its history.

For now I think I can protect myself by protecting the branch.

Thanks for your work BTW, I wouldn't be able to switch browsers so easily without Floccus.

@alexandru commented on GitHub (Jul 23, 2025): @marcelklehr I recovered them, no worries. I'm using multiple browsers, yesterday I've set up a new Vivaldi instance and this is probably what's caused it — especially since I definitely have 2 ore more browsers syncing concurrently. Git's history is what gives me peace of mind that in the worst case (e.g., bookmarks get deleted without my knowledge), I can still recover them due to having its history. For now I think I can protect myself by protecting the branch. Thanks for your work BTW, I wouldn't be able to switch browsers so easily without Floccus.

kerem commented

2026-02-25 22:39:44 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 6, 2025):

The latest release has the fix now. :)

@marcelklehr commented on GitHub (Aug 6, 2025): The latest release has the fix now. :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1336

No description provided.

Rows
Columns