You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few existing store plugins for Git Repo providers - Github, Bitbucket, Gitea, and others - but all of these rely on the underlying API of the service the plugin is built for, which means if a git provider does NOT have a commit API - sr.ht being an example where the only way to commit is via a "git commit, git push" - that provider is unable to be used as a Git Store.
Describe the solution you’d like
While a plugin could be written exclusively for sr.ht that utilizes a toolkit like git-utils [1], I feel it makes more sense to develop a generic store plugin that commits and pushes to a repo cloned to the local file system. This would allow one store plugin to work with all providers that do not offer their own custom commit API.
I'm curious why this hasn't been pursued already as a feature - are there any considerations on why this would not work before I start trying to develop the plugin?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
There are a few existing store plugins for Git Repo providers - Github, Bitbucket, Gitea, and others - but all of these rely on the underlying API of the service the plugin is built for, which means if a git provider does NOT have a commit API - sr.ht being an example where the only way to commit is via a "git commit, git push" - that provider is unable to be used as a Git Store.
Describe the solution you’d like
While a plugin could be written exclusively for sr.ht that utilizes a toolkit like git-utils [1], I feel it makes more sense to develop a generic store plugin that commits and pushes to a repo cloned to the local file system. This would allow one store plugin to work with all providers that do not offer their own custom commit API.
[1] https://www.npmjs.com/package/git-utils
Describe alternatives you’ve considered
No response
Additional context
I'm curious why this hasn't been pursued already as a feature - are there any considerations on why this would not work before I start trying to develop the plugin?
The text was updated successfully, but these errors were encountered: