Skip to content

Update Claude Code action to use GitHub token for authentication, enh…#654

Merged
MervinPraison merged 1 commit intomainfrom
develop
Jun 16, 2025
Merged

Update Claude Code action to use GitHub token for authentication, enh…#654
MervinPraison merged 1 commit intomainfrom
develop

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

@MervinPraison MervinPraison commented Jun 16, 2025

User description

…ancing security and consistency in the workflow.


PR Type

Enhancement


Description

• Replace hardcoded username with dynamic github.actor
• Switch from custom GH_TOKEN to standard GITHUB_TOKEN
• Improve security and consistency in GitHub workflow authentication


Changes walkthrough 📝

Relevant files
Configuration changes
claude.yml
Standardize GitHub token authentication                                   

.github/workflows/claude.yml

• Replace hardcoded username 'MervinPraison' with github.actor

Switch from secrets.GH_TOKEN to secrets.GITHUB_TOKEN
• Update both
Docker registry login and Claude action authentication

+3/-3     

Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Summary by CodeRabbit

    • Chores
      • Updated workflow authentication to use standardized GitHub tokens and dynamic usernames for improved consistency and security.

    …ancing security and consistency in the workflow.
    @gemini-code-assist
    Copy link
    Copy Markdown
    Contributor

    Note

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

    @MervinPraison MervinPraison merged commit 0a48d78 into main Jun 16, 2025
    3 of 12 checks passed
    @coderabbitai
    Copy link
    Copy Markdown
    Contributor

    coderabbitai bot commented Jun 16, 2025

    Caution

    Review failed

    The pull request is closed.

    Walkthrough

    The GitHub Actions workflow for the Claude Code job was updated to replace hardcoded and custom secret references with dynamic variables and standardized GitHub-provided secrets. The Docker login and Claude Code action now use ${{ github.actor }} for the username and ${{ secrets.GITHUB_TOKEN }} for authentication.

    Changes

    File(s) Change Summary
    .github/workflows/claude.yml Updated Docker login to use ${{ github.actor }} and ${{ secrets.GITHUB_TOKEN }}; unified secret usage for Claude Code action.

    Sequence Diagram(s)

    sequenceDiagram
        participant GitHub Actions Workflow
        participant DockerHub
        participant Claude Code Action
    
        GitHub Actions Workflow->>DockerHub: Login (username: ${{ github.actor }}, password: ${{ secrets.GITHUB_TOKEN }})
        GitHub Actions Workflow->>Claude Code Action: Run action (github_token: ${{ secrets.GITHUB_TOKEN }})
    
    Loading

    Possibly related PRs

    Suggested labels

    Review effort 1/5

    Poem

    The tokens now dance in a unified stream,
    No more hardcoded secrets, a maintainer’s dream!
    The actor steps up, credentials in hand,
    While Claude Code runs just as planned.
    🐇✨
    Workflows now flow with dynamic delight—
    Secure and tidy, all through the night!


    📜 Recent review details

    Configuration used: CodeRabbit UI
    Review profile: CHILL
    Plan: Pro

    📥 Commits

    Reviewing files that changed from the base of the PR and between 3c0ba5a and ed8de3b.

    📒 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
    🪧 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
    Copy link
    Copy Markdown

    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

    Token Permissions

    Verify that GITHUB_TOKEN has sufficient permissions for the Claude action and Docker registry operations. The default GITHUB_TOKEN may have different scopes than the custom GH_TOKEN that was previously used.

        password: ${{ secrets.GITHUB_TOKEN }}
    
    - name: Run Claude Code
      id: claude
      uses: ./.github/actions/claude-code-action
      with:
        anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
        github_token: ${{ secrets.GITHUB_TOKEN }}

    @qodo-code-review
    Copy link
    Copy Markdown

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    Possible issue
    Use proper registry authentication token

    Using GITHUB_TOKEN for Docker registry authentication may have insufficient
    permissions for pushing to GitHub Container Registry. Consider using a personal
    access token with appropriate registry permissions stored in secrets.GH_TOKEN
    instead.

    .github/workflows/claude.yml [41]

    -password: ${{ secrets.GITHUB_TOKEN }}
    +password: ${{ secrets.GH_TOKEN }}
    • Apply / Chat
    Suggestion importance[1-10]: 9

    __

    Why: The suggestion correctly identifies a critical potential issue. The default GITHUB_TOKEN may not have the required packages: write permissions to publish to the GitHub Container Registry (ghcr.io). This change could cause the workflow to fail during the image push step, as the PR does not add a permissions block to grant the necessary scope.

    High
    • More

    shaneholloman pushed a commit to shaneholloman/praisonai that referenced this pull request Feb 4, 2026
    Update Claude Code action to use GitHub token for authentication, enh…
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    1 participant