[Solved] Submitting a plugin on behalf of GitHub Organization

Hey all :wave:

I’m looking to publish a plugin on behalf of a GitHub organization, samepage-network, and it appears that the CI failed due to that repository owner not matching my username dvargas92495.

Relevant plugin here: Publish SamePage Extension by dvargas92495 · Pull Request #1342 · obsidianmd/obsidian-releases · GitHub

Would the team be open to a PR amending the release process so that developers could submit extensions on behalf of an organization?

1 Like

I’m not sure which category this post belongs in (I’d have guessed Developers & API but the description emphasizes technical stuff), but it’s definitely not a plugin idea.

If you’re on Discord you might want to pop into one of the appropriate channels there.

Don’t worry, the CI will fail but the obsidian team will look at it anyway. I’m in the exact same situation.

I created a PR that communicates my thoughts here, allowing orgs to publish plugins: Update validate plugin entry to account for publishing on behalf of orgs by dvargas92495 · Pull Request #1376 · obsidianmd/obsidian-releases · GitHub

I didn’t see any appropriate categories when I made the post, so I picked plugin ideas, since it’s an idea for plugins :laughing:

I tried Discord first, and was directed here

Sorry, I wasn’t trying to put you in a loop. :sweat_smile:

I moved the thread to Developers & API as probably the closest to appropriate.

Thank you! We recently merged the PR enabling this

1 Like