Allow non-GitHub repositories for plugins

Developers: Plugin & API
1

Use case or problem

I would like to develop an Obsidian plugin, but I do not want to put my code on GitHub.

Proposed solution

Make it possible to submit plugin code, for example via a URL to a git repository, that does not require using Github?

Quoting ttps://docs.obsidian.md/Plugins/Releasing/Submit+your+plugin#Step+3+Submit+your+plugin+for+review :

repo is the path to your GitHub repository. For example, if your GitHub repo is located at https://github.com/your-username/your-repo-name, the path is your-username/your-repo-name.

I think it should be possible to ask for a Git repository without requiring that it’s a GitHub one, and this will even align the plugin process with Obsidian’s Manifesto (https://obsidian.md/about) by not tying developers into a specific platform.

Related links

Originally raised on GitHub: https://github.com/obsidianmd/obsidian-sample-plugin/issues/152

2 Likes
2

You can put your code somewhere else but you will have to use a Github for plugin distribution. That is unfortunately how the current obsidian infrastructure works on.

We’ve previously had plugins with source hosted on Gitlab, and they were ok to make a Github repo to upload the final builds.

3

Hi Licat, thanks for the response.

I understood that. This is a feature request for an alternative method.

Just like Obsidian promotes file over app to avoid locking users into a platform and alowing them to own their own data, I think the plugin architecture should not require developers to use a specific platform (Microsoft GitHub).

4

I would love that!