Update Claude Code action reference to use local action for improved …

[MervinPraison]

User description

…maintainability

---

PR Type

Enhancement

---

Description

• Update Claude Code workflow to use local action reference
• Replace external Docker image with local action path
• Improve maintainability by using local action implementation

---

Changes walkthrough 📝

	Relevant files
Configuration changes	claude.yml Switch to local Claude Code action                                              .github/workflows/claude.yml • Changed action reference from external Docker image to local action • Updated uses field to point to ./.github/actions/claude-code-action • Maintained same input parameters for API key and GitHub token +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Rate limit exceeded

@qodo-merge-pro[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e09c1b2 and b4831b3.

📒 Files selected for processing (1)

• .github/workflows/claude.yml (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[qodo-code-review]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build (3.10)

Failed stage: Test with pytest [❌]

Failed test name: test_claude_code_tool_import

Failure summary: The action failed because the test test_claude_code_tool_import failed. The test failed due to a missing module import error: "No module named 'context'". Additionally, the test returned False instead of None, suggesting the test function should use assert statements instead of return statements for proper test validation.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1692: Downloading msal_extensions-1.3.1-py3-none-any.whl (20 kB) 1693: Downloading mammoth-1.9.1-py2.py3-none-any.whl (52 kB) 1694: Downloading cobble-0.1.4-py3-none-any.whl (4.0 kB) 1695: Downloading markdownify-1.1.0-py3-none-any.whl (13 kB) 1696: Downloading olefile-0.47-py2.py3-none-any.whl (114 kB) 1697: Downloading python_pptx-1.0.2-py3-none-any.whl (472 kB) 1698: Downloading XlsxWriter-3.2.3-py3-none-any.whl (169 kB) 1699: Downloading speechrecognition-3.14.3-py3-none-any.whl (32.9 MB) 1700: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 32.9/32.9 MB 211.6 MB/s eta 0:00:00 1701: Downloading xlrd-2.0.2-py2.py3-none-any.whl (96 kB) 1702: Installing collected packages: XlsxWriter, xlrd, speechrecognition, portalocker, olefile, isodate, hyperframe, hpack, defusedxml, cobble, youtube-transcript-api, python-pptx, markdownify, mammoth, h2, azure-core, magika, azure-ai-documentintelligence, msal, markitdown, chonkie, qdrant-client, msal-extensions, mem0ai, azure-identity, chromadb 1703: Attempting uninstall: chromadb 1704: Found existing installation: chromadb 0.5.23 1705: Uninstalling chromadb-0.5.23: 1706: Successfully uninstalled chromadb-0.5.23 1707: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. 1708: praisonai-tools 0.0.22 requires chromadb<0.6.0,>=0.5.10, but you have chromadb 1.0.12 which is incompatible. ... 1912: OPENAI_MODEL_NAME: *** 1913: LOGLEVEL: DEBUG 1914: ##[endgroup] 1915: ============================= test session starts ============================== 1916: platform linux -- Python 3.10.18, pytest-8.4.0, pluggy-1.6.0 -- /opt/hostedtoolcache/Python/3.10.18/x64/bin/python 1917: cachedir: .pytest_cache 1918: rootdir: /home/runner/work/PraisonAI/PraisonAI/src/praisonai 1919: configfile: pytest.ini 1920: plugins: langsmith-0.3.45, asyncio-1.0.0, anyio-4.9.0, cov-6.2.1 1921: asyncio: mode=auto, asyncio_default_fixture_loop_scope=function, asyncio_default_test_loop_scope=function 1922: collecting ... collected 90 items 1923: tests/unit/agent/test_mini_agents_fix.py::test_context_processing PASSED [ 1%] 1924: tests/unit/agent/test_mini_agents_sequential.py::test_mini_agents_sequential_data_passing PASSED [ 2%] 1925: tests/unit/agent/test_type_casting.py::TestAgentTypeCasting::test_cast_arguments_already_correct_type PASSED [ 3%] 1926: tests/unit/agent/test_type_casting.py::TestAgentTypeCasting::test_cast_arguments_boolean_conversion PASSED [ 4%] 1927: tests/unit/agent/test_type_casting.py::TestAgentTypeCasting::test_cast_arguments_conversion_failure_graceful PASSED [ 5%] 1928: tests/unit/agent/test_type_casting.py::TestAgentTypeCasting::test_cast_arguments_float_conversion PASSED [ 6%] ... 1942: tests/unit/test_approval_basic.py::test_approval_callback PASSED [ 22%] 1943: tests/unit/test_approval_basic.py::test_agent_integration PASSED [ 23%] 1944: tests/unit/test_approval_interactive.py::test_shell_command_approval SKIPPED [ 24%] 1945: tests/unit/test_approval_interactive.py::test_python_code_approval SKIPPED [ 25%] 1946: tests/unit/test_approval_interactive.py::test_file_operation_approval SKIPPED [ 26%] 1947: tests/unit/test_approval_interactive.py::test_auto_approval_callback PASSED [ 27%] 1948: tests/unit/test_approval_interactive.py::test_auto_denial_callback PASSED [ 28%] 1949: tests/unit/test_async_agents.py::TestAsyncAgents::test_async_tool_creation PASSED [ 30%] 1950: tests/unit/test_async_agents.py::TestAsyncAgents::test_async_task_execution PASSED [ 31%] 1951: tests/unit/test_async_agents.py::TestAsyncAgents::test_async_callback PASSED [ 32%] 1952: tests/unit/test_async_agents.py::TestAsyncAgents::test_async_agents_start PASSED [ 33%] 1953: tests/unit/test_async_agents.py::TestAsyncAgents::test_mixed_sync_async_tasks PASSED [ 34%] 1954: tests/unit/test_async_agents.py::TestAsyncAgents::test_workflow_async_execution PASSED [ 35%] 1955: tests/unit/test_async_agents.py::TestAsyncTools::test_async_search_tool PASSED [ 36%] 1956: tests/unit/test_async_agents.py::TestAsyncTools::test_async_tool_with_agent PASSED [ 37%] 1957: tests/unit/test_async_agents.py::TestAsyncTools::test_async_tool_error_handling PASSED [ 38%] 1958: tests/unit/test_async_agents.py::TestAsyncMemory::test_async_memory_operations PASSED [ 40%] 1959: tests/unit/test_claude_code_integration.py::test_claude_code_tool_import FAILED [ 41%] 1960: =================================== FAILURES =================================== 1961: _________________________ test_claude_code_tool_import _________________________ 1962: Expected None, but test returned False. Did you mean to use `assert` instead of `return`? 1963: ----------------------------- Captured stdout call ----------------------------- 1964: ❌ Failed to import claude_code_tool: No module named 'context' 1965: =========================== short test summary info ============================ 1966: FAILED tests/unit/test_claude_code_integration.py::test_claude_code_tool_import - Failed: Expected None, but test returned False. Did you mean to use `assert` instead of `return`? 1967: !!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!! 1968: ============= 1 failed, 31 passed, 5 skipped, 6 warnings in 13.06s ============= 1969: 🧪 Running fast tests... 1970: Running command: python -m pytest tests/unit/ -m not slow --tb=short --disable-warnings -x 1971: ❌ fast tests failed! 1972: ##[error]Process completed with exit code 1. 1973: Post job cleanup.

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Action The workflow now references a local action at ./.github/actions/claude-code-action but there's no evidence this local action exists in the repository. This could cause the workflow to fail if the action directory or required files are missing. uses: ./.github/actions/claude-code-action with: Unused Step The Docker login step appears to be no longer needed since the workflow switched from using a Docker image to a local action, but the login step is still present and may be redundant. uses: docker/login-action@v3 with: registry: ghcr.io username: ${{ github.actor }} password: ${{ secrets.GH_TOKEN }}

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Verify local action exists The workflow references a local action that may not exist in the repository. Verify that the action directory exists and contains the required action.yml file with proper metadata and implementation. .github/workflows/claude.yml [42] +uses: ./.github/actions/claude-code-action - Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out that the workflow now depends on a local action. Since the PR diff only shows the workflow file, it is crucial to verify that the action files at ./.github/actions/claude-code-action are also part of the repository, as their absence would break the workflow.	Medium
More