Netlify Editorial Workflow with GitLab Backend
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Enabling the Editorial Worfklow method from Netlify CMS
Note: issues from GitHub repository
- https://github.com/netlify/netlify-cms/issues/568
- https://github.com/netlify/netlify-cms/pull/1817 (first PR, abandoned)
- https://github.com/netlify/netlify-cms/pull/2409 (Current PR)
Intended users
All users who are using GitLab and CI/CD runners for JAMstack site deployments.
Further details
The JAM stack is a popular way to deploy sites without a traditional backend. Netlify CMS makes the editing process much easier, especially for non-technical users. Currently Netlify CMS Editorial Workflow is available for GitHub, but needs more work for GitLab integration.
Proposal
Can someone with a better understanding of the GitLab ecosystem help plan a path of what tests and procedures are needed to move forward with this implementation? Netlify and Gitlab made an announcment last year to support the backend authenticatino, but not the branch-features of editorial workflow. I can volunteer time to this project, with potential some teammates as well, but will need some collaboration with GitLab authors on how to proceed.
Testing
It seems like the implementation for GitHub is already complete, and would need to mirror the GitHub git API calls to GitLab. The pull request on Netlify seems to emphasize a need for GitLab testing before introducing the branch.
What is the type of buyer?
Users of Netlify of GitLab pages.
Links / references
https://www.netlifycms.org/docs/configuration-options/#publish-mode