Skip to content

Link security tracking issue to blog MR

Steve Abrams requested to merge delivery19737-fix-issue-link into master

What does this MR do and why?

  • Link security tracking issue to blog MR

When there is security content in a blog MR, link the security release tracking issue instead of the patch release issue.

Related to gitlab-com/gl-infra/delivery#19737 (closed)

Testing

I ran the release:patch_blog_post rake task with the :combined_blog_post feature flag enabled and disabled to show the result for when there is and is not security content:

FF Enabled - includes security content

~ TEST=true RELEASE_BOT_VERSION_TOKEN=$VERSION_TOKEN RELEASE_BOT_PRODUCTION_TOKEN=$PROD_TOKEN be rake release:patch_blog_post
....
Add blog post for 16.5.1, 16.4.2, 16.3.6 patch release.


- [ ] Complete any sections of the blog post that have TODO in their content.


Security release tracking issue: https://gitlab.com/gitlab-org/gitlab/-/issues/426612

FF Disabled - only patch content

The test.gitlab.com comes from the dry run setting.

~ TEST=true RELEASE_BOT_VERSION_TOKEN=$VERSION_TOKEN RELEASE_BOT_PRODUCTION_TOKEN=$PROD_TOKEN be rake release:patch_blog_post
....
Add blog post for 16.5.1, 16.4.2, 16.3.6 patch release.


Patch issue: test.gitlab.com

Author Check-list

  • [-] Has documentation been updated?
Edited by Steve Abrams

Merge request reports