Skip to content
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

Implement editorial workflow for Gitea / Forgejo backend #7115

Open
privatemaker opened this issue Feb 21, 2024 · 3 comments
Open

Implement editorial workflow for Gitea / Forgejo backend #7115

privatemaker opened this issue Feb 21, 2024 · 3 comments
Labels
area: extensions/backends/gitea area: ui/editorial-workflow type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@privatemaker
Copy link
Contributor

Now that there is a Gitea / Forgejo Backend supported, I open this issue proposal to request adding publish_mode: editorial_workflow support to it.

Maybe @denyskon who's fantastic work contributed Gitea support 👍🏻 😄 can comment on the viability of this task? Did you notice anything quirks that might make it not feasible?

@privatemaker privatemaker added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Feb 21, 2024
@denyskon
Copy link
Contributor

I think a few API endpoints are missing in Gitea to achieve that. In general, the Gitea API is pretty compatible with the GitHub API, so if we find out the missing endpoints and implement them in Gitea (I could maybe help there), it should be feasible.

(also see StaticJsCMS/static-cms#1047)

@privatemaker
Copy link
Contributor Author

Thanks for the quick reply 🌟 Since you know the Decap code (and I do not), if you make a list of those endpoints, I'm happy to open isses on Gitea tracker and perhaps even bug some of my Go developer friends to nudge this forward...

@tobru
Copy link

tobru commented Aug 27, 2024

@denyskon Do you have any insights which API endpoints are missing? Or do you have any pointers on how to find out which ones are missing? Once we know that, we can work with Gitea/Forgejo to get them implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: extensions/backends/gitea area: ui/editorial-workflow type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

4 participants