Hi fellow developers!
I’ve opened a merge request for a new plugin: Add plugin: Native RTL by Bip901 · Pull Request #6913 · obsidianmd/obsidian-releases · GitHub
It’s been 3 months since I’ve made the (small) changes requested, yet it’s still waiting to be merged.
It’s a relatively small plugin (just 1 TypeScript file with ~200 lines); If anyone with the appropriate permissions is available to take a look at it, it would be much appreciated!
The bot hasn’t detected that you’ve made the requested changes, so it hasn’t been moved back into the human review queue, so no humans are looking at it.
Oh 
Thank you! Hope it’ll get picked up now
They are currently 3+ months behind on the github repo. I have been waiting 2.5 months so far. Haven’t heard a word from them yet. Same for many others.
It’s unrealistic for anyone to develop a plugin and only have it appear in the marketplace three entire months later.
Why is obsidian SO SLOW at going through plugins?
It IS the only thing keeping this app alive, yet plugin creators are treated as third class citizens.
Because there are more submissions that what we can chew. Submitting a plugin is free.
I disagree that it IS the only thing that is keeping the app alive, but okay. The team has been making progress in increasing the level automation but the final part of the review is still done manually.
I disagree that it IS the only thing that is keeping the app alive,
Really?
Let’s try a simple thought experiment, shall we?
Suppose you completely remove Obsidian’s plugin marketplace.
How many people will still use Obsidian?
My guess is roughly 5% of the current user base. Maybe even less.
The team should increase focus on plugin approval.
This timeline is not acceptable.
I noticed the plugin release GitHub Repo is backed up for like a month.
How long does it usually take to get approved?
There are many factors, so we can’t provide any estimates.
Some of these factors are:
Is there a list of the most common issues that come up during review ?
Well, I submitted one.
I have at least three others I want to submit. I was going to wait for the first one to get approved just to see if there is anything I learn from the process before submitting the other ones. But, that may not make sense if it could be a month or two before they are approved, as the other ones will just be in a queue forever.
If anybody has interest in contributing or using ahead of the release on the Community Plugins marketplace, just discuss on GitHub or clone or fork and git going!
do you mean Site vs Cite ? (image #4)
No, the plugin is about Citations. It creates a vault wide registry and makes sure each unique link gets its own unique hex code.
Clever play on words.
Hello. I consolidated a few threads into this one. A few notes.
We do value third-party plugin. We have taken steps in the past months to reduce the review time. These range from improving/increasing the automation with a new ReviewBot and with hiring additional reviewers.
We have so far intentionally kept the plugin submission free for developers and the final stages of the review process is still manual. These two things alongside the rise of vibe-coding has created the backlog you see right now. We will try to improve more in the coming months.
@sojedi7030 (and all the alt accounts you are creating to complain), I do not like that you claim that I said thing that I never said NOR that can be implied from the things that I said. Please, refrain from twisting my response (or flat-out inviting things) just to push your agenda.
Also for the record, user @sojedi7030 was banned not for censorship reasons nor for their opinions, but because of multiple breaches of our code of conduct, even after a warning. As well as giving demanding ultimatums, and making rather rude and hateful political comments. (Ordinarily we wouldn’t call out a user like this, but they continue to make alt accounts and misconstruing the situation.)
Hi everyone,
I’m in a similar situation and would appreciate some guidance on how to trigger a rescan from ObsidianReviewBot.
I submitted my plugin (PR #8779) on November 30th. The bot scanned my code on December 1st (18:50 UTC) and flagged some eslint issues. I fixed all of them in release v0.7.2, published just 47 minutes after the scan.
Since then, I’ve published 7 more releases (v0.7.3 through v0.8.1), but the bot hasn’t rescanned in over 3 days. The labels still show “Changes requested” even though the issues were resolved.
I’ve tried:
Is there something specific I need to do to trigger a rescan?
Any help would be greatly appreciated. Thank you for your time!
Fair enough! I’m happy with BRAT as a way for people to access plugins before the team has a chance to get to them.