From 236cfa31064da5b4e02dd1a447d6abb737e208e3 Mon Sep 17 00:00:00 2001 From: sobolevn Date: Wed, 16 Oct 2024 10:17:39 +0300 Subject: [PATCH] chore(ci): fix the `pr_merged.yml` workflow (#3811) --- .github/workflows/pr-merged.yml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.github/workflows/pr-merged.yml b/.github/workflows/pr-merged.yml index dd678f7c1f..c13039ea8d 100644 --- a/.github/workflows/pr-merged.yml +++ b/.github/workflows/pr-merged.yml @@ -19,11 +19,8 @@ jobs: script: | const prNumber = context.payload.number const branch = context.baseRef - # TODO: `develop` no longer exists. Need a new way to determine if the - # change will be introduced in a major, minor, or patch release. - # possibly conventional commit standards in the PR title or by labels? - const isDevelop = branch === "develop" - const commentBody = `\nThis issue has been closed in #${prNumber}. The change will be included in the upcoming ${isDevelop ? "minor" : "patch"} release.` + // TODO: use semantic commits to specify the exact version, when it will be released + const commentBody = `\nThis issue has been closed in #${prNumber}. The change will be included in upcoming releases.` const query = `query($number: Int!, $owner: String!, $name: String!) { repository(owner: $owner, name: $name) { pullRequest(number: $number) {