Print reviewer to check, fix open pr step

[meritmalling]

Please explain how to summarize this PR for the Changelog:

NA

Tell code reviewer how and what to test:

NA

Fixes open pr step! 🤞

[coderabbitai]

Walkthrough

The changes introduce a new step in the GitHub Actions workflow for creating pull requests related to changelog updates. A step named "Print reviewers" has been added to output reviewer information. Additionally, the pull request creation process has been modified to utilize the gh pr create command, allowing for updated parameters and a more streamlined command-line approach.

Changes

Files	Change Summary
.github/workflows/cl-create.yml	Added a new step "Print reviewers" and modified the "Create pull request" step to use gh pr create with updated parameters.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7d5f101 and 1798286.

Files selected for processing (1)

• .github/workflows/cl-create.yml (2 hunks)

Additional context used

actionlint

.github/workflows/cl-create.yml

88-88: this step is for running action since it contains at least one of "uses", "with" keys, but also contains "run" key which is used for running shell command

(syntax-check)

---

100-100: key "env" is duplicated in element of "steps" section. previously defined at line:79,col:9

(syntax-check)

Additional comments not posted (3)

.github/workflows/cl-create.yml (3)

56-57: LGTM!

The "Print reviewers" step is correctly implemented and enhances visibility into the reviewers involved in the process.

The code changes are approved.

---

88-101: Fix the syntax issue and remove the duplicated env key.

The "run" key should not be used in a step that also uses the "uses" key. Additionally, the "env" key is duplicated in the step.

Apply this diff to fix the issues:

-        run: |
-          gh pr create \
-            --repo ${{ steps.set_vars.outputs.destination_repo }} \
-            --base main \
-            --head changelog/${{ github.event.release.tag_name }} \
-            --title "Changelog update changelog/${{ github.event.release.tag_name }}" \
-            --reviewer ${{ steps.get_reviewers.outputs.reviewers }} \
-            --body "@coderabbitai: ignore
-            This pull request has been automatically created to update the changelog.
-      
-            Edit the YYMMDD.mdx file with any updates.
-            Committing your changes will trigger the update changelog workflow, which will pull your updates into the main changelog files."
-        env:
-          GH_TOKEN: ${{ steps.changelog_token.outputs.token }}
+        uses: actions/github-script@v4
+        with:
+          script: |
+            gh pr create \
+              --repo ${{ steps.set_vars.outputs.destination_repo }} \
+              --base main \
+              --head changelog/${{ github.event.release.tag_name }} \
+              --title "Changelog update changelog/${{ github.event.release.tag_name }}" \
+              --reviewer ${{ steps.get_reviewers.outputs.reviewers }} \
+              --body "@coderabbitai: ignore
+              This pull request has been automatically created to update the changelog.
+        
+              Edit the YYMMDD.mdx file with any updates.
+              Committing your changes will trigger the update changelog workflow, which will pull your updates into the main changelog files."
+          env:
+            GH_TOKEN: ${{ steps.changelog_token.outputs.token }}

Tools

actionlint

88-88: this step is for running action since it contains at least one of "uses", "with" keys, but also contains "run" key which is used for running shell command

(syntax-check)

---

100-100: key "env" is duplicated in element of "steps" section. previously defined at line:79,col:9

(syntax-check)

---

88-88: Fix the syntax issue.

The "run" key should not be used in a step that also uses the "uses" key.

Apply this diff to fix the issue:

-        run: |

Tools

actionlint

88-88: this step is for running action since it contains at least one of "uses", "with" keys, but also contains "run" key which is used for running shell command

(syntax-check)

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1