-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitea backend for CMS #271
Comments
We've also been having trouble getting PKCE to work clientside: https://discourse.gitea.io/t/oauth-pkce-example/6573 Sounds like you can't omit the |
There's been progress on both the API endpoint and PKCE client secret: decaporg/decap-cms#1109 (comment) 🎉
|
In testing this, I was getting the following error after being redirected back to my website:
I forgot that you need to explicitly set the
|
Gitea support should be available in v0.7.16 🎉 Just note we added a new
The Note that since the APIs have not diverged too much at this point, this release also supports the Gitea fork Forgejo and you can use that as a provider name if you prefer. |
The people have spoken and they want Gitea backend support for the CMS: https://twitter.com/plentico/status/1615857323292987397
Blocker: Can't commit multiple files to a generic endpoint using the API: go-gitea/gitea#14619
Per these API Docs there are only the 2 following methods for manipulating repo files:
/repos/{owner}/{repo}/contents/{filepath}
Update a file in a repository (link)/repos/{owner}/{repo}/contents/{filepath}
Create a file in a repository (link)The text was updated successfully, but these errors were encountered: