Inquiry about plugin review status: "1 workflow awaiting approval"

First, search the help docs and this forum. Maybe your question has been answered! The debugging steps can help, too. Still stuck? Delete this line and proceed.

What I’m trying to do

I am in the process of submitting my first plugin, ObsiMap, to the official community plugin list. I first submitted this PR on December 31, 2025, and I want to ensure that my submission is still on the right track.
Currently, as shown in the attached screenshots, the PR is labeled “Ready for review,” but it has been stuck on “1 workflow awaiting approval” for more than two weeks. Additionally, the ObsidianReviewBot unassigned itself about two weeks ago, and there has been no update or human assignee since then. Given that the initial submission was months ago and this specific state has persisted for a while, I want to confirm if this is a normal part of the current queue or if there is any action I should take to proceed.

Things I have tried

I have confirmed that there are no merge conflicts with the base branch and all files (including manifest.json) follow the guidelines.

I searched the forum for similar cases and learned that workflow approval requires maintainer intervention.
I have been patiently monitoring the PR since late December, but since the status hasn’t changed for over two weeks despite being marked “Ready for review,” I am reaching out to verify if I’ve missed any steps.
I checked for any previous maintainer comments, but the conversation remains empty.

I’m going to move this to Developers: Plugin & API.

Hopefully someone can answer. Good luck!

1 Like

You did a bad merge, your plugin entry is no longer in the file.
Please fix that, and then don’t touch the files after that, we will handle the merge conflicts when the we merge the plugin.

No ETA on the human review, we have been swamped with new plugin submissions.

2 Likes

Thanks for the quick reply! Since I’m not very familiar with GitHub, I had been manually resolving merge conflicts myself, but I now realize that was the wrong approach. Thanks to your guidance, the PR now shows “No conflicts with base branch.” I will leave it as is from now on. Much appreciated!