[REPO]: Remove link to obsidian sample repository

[johannrichard]

@jsonMartin hope you're doing well. I wondered if you ever considered severing the "link" to the original sample-plugin repository of this repo? It's mostly a beauty issue, as it would remove the glaring invite to create a PR to the "upstream" sample plugin or "sync the fork". Of course, feel free to close this of course if you don't (want to) bother.

[jsonMartin]

Hey @johannrichard ! Sure, I'd be happy to help with this. I just tried to sever the fork as requested, but the button is disabled because there are five existing child forks:

If you happen to know of another way I can sever the link while these child forks exist, please let me know and I'll give it a shot!

P.S. I know I've been AWOL for many months due to a grueling schedule and haven't shared my appreciation for all of your hard work, so I just wanted to take a moment to say thank you for doing such a great job maintaining and improving this plugin! Really appreciate it 🙏🏼

[johannrichard]

Thanks @jsonMartin! Delighted to do so, and glad to hear you approve of the direction this has taken.

As for the forks: aw shucks, it looks indeed like these people would first have to delete / remove their fork (not sure if this is something that can be done easily for fossabot …). I will investigate a bit further, but I fear this might be more difficult than I thought.

[johannrichard]

Request to delete / leave readwise-mirror fork network

@jaxley, @shabegom, @tdnzr, @thomasvs: You all forked the readwise-mirror repository at some point in the past. We would like to sever its ties to the obsidian/sample-plugin repository but can't do so because of the forks that still exist. Would you mind checking if a) your fork is still needed, and if not, b) consider deleting it, or – if you want to keep it - c) leave the fork network with your fork first?

Here are the direct links to your forks:

• @jaxley : https://github.com/jaxley/readwise-mirror (I see you made a commit re:filenames. We have quite improved the code for filename generation. If you still use the plugin and think this still needs fixing, let me know, happy to look into it).
• @shabegom: https://github.com/shabegom/readwise-mirror
• @tdnzr: https://github.com/tdnzr/readwise-mirror
• @thomasvs: https://github.com/thomasvs/readwise-mirror

Thanks for your help with that!

[shabegom]

Deleted my fork

[johannrichard]

If you happen to know of another way I can sever the link while these child forks exist, please let me know and I'll give it a shot!

@jsonMartin the nuclear option would be to turn this into a private repository and then make it public again

Changing a public repository to a private repository

If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new upstream repository and all other repositories are forked off of this new upstream. Subsequent pull requests go to this new upstream repository.

In other words, a public repository's forks will remain public in their own separate repository network even after the upstream repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate access permissions to pull changes from and submit pull requests to the (now private) upstream repository—even though they didn't need those permissions before.

However, as the linked article explains, this has an impact on stars, favorites, and the like. So I'd say let's first try the above.

[jaxley]

Hey, thanks for reaching out. I'll take a look right now. Jason Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Monday, 09/29/25 at 12:21 Johann Richard ***@***.***> wrote: johannrichard left a comment [(jsonMartin/readwise-mirror#74)](#74 (comment)) Request to delete / leave readwise-mirror fork network ***@***.***(https://github.com/jaxley), ***@***.***(https://github.com/shabegom), ***@***.***(https://github.com/tdnzr), ***@***.***(https://github.com/thomasvs): You all forked the readwise-mirror repository at some point in the past. We would like to sever its ties to the obsidian/sample-plugin repository but can't do so because of the forks that still exist. Would you mind checking if a) your fork is still needed, and if not, b) consider deleting it, or – if you want to keep it - c) leave the fork network with your fork first? Here are the direct links to your forks: - ***@***.***(https://github.com/jaxley) : https://github.com/jaxley/readwise-mirror (I see you made a commit re:filenames. We have quite improved the code for filename generation. If you still use the plugin and think this still needs fixing, let me know, happy to look into it). - ***@***.***(https://github.com/shabegom): https://github.com/shabegom/readwise-mirror - ***@***.***(https://github.com/tdnzr): https://github.com/tdnzr/readwise-mirror - ***@***.***(https://github.com/thomasvs): https://github.com/thomasvs/readwise-mirror Thanks for your help with that! — Reply to this email directly, [view it on GitHub](#74 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AADFIM4NTMC2ZBY424I3OGT3VGBCVAVCNFSM6AAAAACFISIQS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBYGY4TKNBUGY). You are receiving this because you were mentioned.Message ID: ***@***.***>

[tdnzr]

Have deleted my forked repository.

[thomasvs]

I only had a few README.md changes, I sent you a pull request for those, then left the fork network.

[johannrichard]

@jsonMartin you might want to try again. In case the fossabot/readwise-mirror is in the way: I have not yet figured out how the fossabot/readwise-mirror can be removed, but I suspect deleting the project at https://fossa.com might be one way to remove it (assuming it is yours).

[johannrichard]

Update: I had a fossabot fork on one of my repositories too. Once I had deleted the project in fossa.com, I asked their support to delete the fork, which they did quickly.

[jsonMartin]

I don't recall ever adding Fossa Bot myself, not sure how it showed up. I created an account on fossa.com, but I'm not seeing any way to delete the project there.

And, looks like there are a few other inactive forks, not just Fossa bot:

So, instead I opened a support ticket directly with Github seeing if they can help me with this. I'll keep you posted with the results!

[jsonMartin]

@johannrichard this should be unlinked from obsidianmd/obsidian-sample-plugin:master now!

Double checked and it shows zero active forks, and the API link for api.github.com is showing fork: false for this repo.

LMK if you run into any more issues with this, but closing as completed!