Publish the blog post to the security repository if there are security changes
Overview
Currently, BlogMergeRequest
uses GitlabClient
to create the MR, which means it will always be created on the public repository
With the inclusion of security changes, we need to add the ability for the project to be the security project so the merge request is not opened publicly.
Proposal
Refactor BlogMergeRequest
so the merge request is opened on the security project of Project::WWWGitlabCom
when security changes are included in the blog post
- A helper,
#includes_security_content?
is available onBlogMergeRequest
to help know if there are security changes or not and if thecombined_blog_post
feature flag is enabled.
Edited by Steve Abrams