Skip to content

Reduce complexity of detectBlogPostMergeRequest() in scripts/prepare-release-checklist-issue

What does this MR do?

Decreases complexity of scripts/prepare-release-checklist-issue#detectBlogPostMergeRequest(), which causes current master pipelines to fail.

Why was this MR needed?

Caused by !1135 (merged).

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Merge request reports