fixing yaml syntax for claude code github actions

[allisoneer]

Important

Fix YAML syntax in GitHub Actions workflows by changing allowed_tools to a pipe-separated block format.

• YAML Syntax Fix:
  • Changed allowed_tools from bracketed array to pipe-separated block in claude-code-review.yml, claude-comment-response.yml, and claude-pr-creation.yml.
  • Ensures proper YAML syntax and improves readability.

^{This description was created by for 18b4b77. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 18b4b77 in 41 seconds. Click for details.

• Reviewed 147 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/claude-code-review.yml:25

• Draft comment:
  Using a block literal (|- mode) for allowed_tools improves YAML validity compared to the bracketed list. Confirm that the downstream action correctly parses newline‐separated commands.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

2. .github/workflows/claude-comment-response.yml:18

• Draft comment:
  Allowed_tools is now defined as a block literal. Ensure that the multiline string with newline-separated tool commands is supported by the action.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

3. .github/workflows/claude-pr-creation.yml:27

• Draft comment:
  The allowed_tools section now uses a block literal which should resolve YAML syntax issues. Verify that tool commands, separated by newlines, are processed as expected.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

Workflow ID: wflow_FzG7JtyRkZmhFJYh

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}