Skip to content

Conversation

@furqanahmadrao
Copy link

This pull request updates the CI/CD pipeline setup in the README.md to improve integration and configuration for Claude Code Router, focusing on expanded event triggers, provider configuration, and enhanced workflow steps. The changes make the workflow more robust, flexible, and ready for multi-provider support, specifically adding Gemini as a provider and improving diagnostics and permissions.

Workflow trigger and permissions improvements:

  • Expanded workflow triggers to include pull_request_review_comment, issues, and pull_request_review events, enabling Claude to respond to more types of interactions.
  • Added the actions: read permission to allow Claude to access CI results on pull requests.

Provider and router configuration enhancements:

  • Updated the router configuration to use Gemini as a provider, including setting the API key via secrets and specifying the model (gemini-2.5-flash), with a new router default and additional logging options.
  • Changed the router startup to use the latest version, added health checks after startup, and improved environment variable handling for provider keys.

Workflow usability and diagnostics:

  • Upgraded the Claude Code GitHub Action to v1 and updated arguments to allow expanded tool usage and permissions.

@furqanahmadrao
Copy link
Author

Hi 👋

I had a question about something I noticed while testing the workflow.

When the agent (Claude) replies to comments on issues or pull requests, it correctly uses the Claude identity with its name and avatar.

But when it performs tasks like creating pull requests or pushing commits, those actions show up as coming from github-actions[bot] instead of the Claude account.

I checked the workflow file and didn’t find any explicit line setting GITHUB_TOKEN, so it might be using the default token provided by GitHub Actions.

Do you know if there’s a way to make the agent use its own GitHub token or app identity for creating PRs and commits?

Just wanted to confirm whether this behavior is expected or something that could be adjusted. Thanks for your time — and for the awesome project! 🙏

@furqanahmadrao furqanahmadrao closed this by deleting the head repository Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant