-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(backend): add gitea backend #6808
Conversation
✅ Deploy Preview for decap-www ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This is very WIP, I neither tested it enough nor did I ensure I did not break tests. I will notify when the PR is ready, for now it's just for the ones who're curious if there's something happening. |
This comment was marked as outdated.
This comment was marked as outdated.
@martinjagodic I resolved the conflicts and changed the naming to match the recent changes. One question, as this is my first time working with such a monorepo: do I have to bump the version number for the |
Thanks, @denyskon. Versions are bumped automatically when we create a release, so you don't need to do that. |
✅ Deploy Preview for cms-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @denyskon I know it's been a while... Are you willing to dive into why tests are failing? |
@martinjagodic Sorry, I didn't notice the lint failure, and build failed because of a dependency update on master. It should all pass now :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! We could add some e2e tests, but since they are probably awaiting a huge overhaul I think we can add that later.
Summary
Introduces Gitea as new backend for Decap CMS. Fixes #1109
Checklist
A picture of a cute animal (not mandatory but encouraged)