⚠️ Potential issue

Workflow fails to parse – convert the multi-line run script to a block scalar.

actionlint / yamllint correctly report a YAML syntax error because the multi-line curl command is written as a plain scalar; the embedded : in the header line is parsed as a new mapping key.
The job will never start.

-      - run: curl \
-          -H "Authorization: token ${{ github.token }}" \
-          -d '{"assignees": ["${{ github.event.comment.user.login }}"]}' \
-          https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees
+      - run: |
+          curl -sS \
+            -H "Authorization: token ${{ github.token }}" \
+            -H "Content-Type: application/json" \
+            -d "{\"assignees\": [\"${{ github.event.comment.user.login }}\"]}" \
+            "https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees"

Block-scalar (|) formatting eliminates the syntax error and makes the script easier to read.
Adding -H "Content-Type: application/json" and quoting the URL are optional polish but keep the command self-contained.

In .github/workflows/comment-commands.yml around lines 18 to 23, the multi-line
curl command under the run step is written as a plain scalar causing YAML syntax
errors due to unescaped colons. Convert the multi-line run script to use a block
scalar (|) to properly format the command as a literal block. Optionally, add
the header "Content-Type: application/json" and quote the URL string to improve
clarity and completeness.

@coderabbitai can you open a PR with those changes?

@ShaharNaveh I'll plan the code changes to fix the YAML syntax error in the workflow file. Another agent will execute these changes and create the PR for you.

Task: Fix YAML syntax error in comment-commands.yml

• Convert multi-line curl command to use block scalar format
• Add proper escaping and formatting
• Include Content-Type header and quote URL for completeness

The changes will fix the YAML parsing error by using proper block scalar formatting, and I've included the Content-Type header and URL quoting for better clarity and completeness as suggested in my previous comment.

Learnt from: ShaharNaveh
PR: RustPython/RustPython#5932
File: .github/workflows/comment-commands.yml:18-24
Timestamp: 2025-07-10T10:08:43.304Z
Learning: In GitHub Actions workflows for the RustPython project, the maintainer ShaharNaveh prefers to keep workflows simple and doesn't mind if steps fail when the desired state is already achieved (e.g., user already assigned to an issue). Avoid suggesting complex error handling for edge cases they don't consider problematic.

⏳ Preparing changes...

A summary of the changes CodeRabbit can apply:

• Fix the YAML syntax error in the GitHub Actions workflow by converting the multi-line curl command to block scalar format with proper indentation and escaping, ensuring correct parsing of the Authorization header.

• ✅ Create PR with these edits
• 📌 Create commit in current branch
• 📋 Get copyable edits

@coderabbitai Create PR with these edits

@coderabbitai get me a copyable edit

Here are the copyable edits based on the planned changes:

Copyable Edits

.github/workflows/comment-commands.yml

@@ -17,7 +17,9 @@
 
    steps:
      # Using REST API and not `gh issue edit`. https://github.com/cli/cli/issues/6235#issuecomment-1243487651
-     - run: curl \
-         -H "Authorization: token ${{ github.token }}" \
-         -d '{"assignees": ["${{ github.event.comment.user.login }}"]}' \
-         https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees
+     - run: |
+         curl -sS \
+           -H "Authorization: token ${{ github.token }}" \
+           -H "Content-Type: application/json" \
+           -d "{"assignees": ["${{ github.event.comment.user.login }}"]}" \
+           "https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees"

• ✅ Create PR with these edits
• 📌 Create commit in current branch