Skip to content

Commit

Permalink
chore(ci): fix the pr_merged.yml workflow (#3811)
Browse files Browse the repository at this point in the history
  • Loading branch information
sobolevn authored Oct 16, 2024
1 parent c5421e5 commit 236cfa3
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions .github/workflows/pr-merged.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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 = `<!--closing-comment-->\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 = `<!--closing-comment-->\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) {
Expand Down

0 comments on commit 236cfa3

Please sign in to comment.