Skip to content

Add Claude Code GitHub Workflow#2

Merged
pedramamini merged 2 commits intomainfrom
add-claude-github-actions-1764002617223
Nov 24, 2025
Merged

Add Claude Code GitHub Workflow#2
pedramamini merged 2 commits intomainfrom
add-claude-github-actions-1764002617223

Conversation

@pedramamini
Copy link
Collaborator

🤖 Installing Claude Code GitHub App

This PR adds a GitHub Actions workflow that enables Claude Code integration in our repository.

What is Claude Code?

Claude Code is an AI coding agent that can help with:

  • Bug fixes and improvements
  • Documentation updates
  • Implementing new features
  • Code reviews and suggestions
  • Writing tests
  • And more!

How it works

Once this PR is merged, we'll be able to interact with Claude by mentioning @claude in a pull request or issue comment.
Once the workflow is triggered, Claude will analyze the comment and surrounding context, and execute on the request in a GitHub action.

Important Notes

  • This workflow won't take effect until this PR is merged
  • @claude mentions won't work until after the merge is complete
  • The workflow runs automatically whenever Claude is mentioned in PR or issue comments
  • Claude gets access to the entire PR or issue context including files, diffs, and previous comments

Security

  • Our Anthropic API key is securely stored as a GitHub Actions secret
  • Only users with write access to the repository can trigger the workflow
  • All Claude runs are stored in the GitHub Actions run history
  • Claude's default tools are limited to reading/writing files and interacting with our repo by creating comments, branches, and commits.
  • We can add more allowed tools by adding them to the workflow file like:
allowed_tools: Bash(npm install),Bash(npm run build),Bash(npm run lint),Bash(npm run test)

There's more information in the Claude Code action repo.

After merging this PR, let's try mentioning @claude in a comment on any PR to get started!

@pedramamini pedramamini merged commit 4045294 into main Nov 24, 2025
1 check passed
@pedramamini pedramamini deleted the add-claude-github-actions-1764002617223 branch November 24, 2025 16:44
This was referenced Dec 6, 2025
@claude claude bot mentioned this pull request Dec 26, 2025
chr1syy referenced this pull request in chr1syy/Maestro Jan 12, 2026
chr1syy referenced this pull request in chr1syy/Maestro Jan 13, 2026
reachraza added a commit that referenced this pull request Feb 6, 2026
Address PR review feedback:

- Issue #1: Add early returns in openModal, closeModal, and closeAll
  to skip Map recreation when state hasn't changed. Prevents
  unnecessary selector re-evaluations across all subscribers.

- Issue #2: Add JSDoc to useModalActions() explaining that the ~40
  selector subscriptions are intentionally transitional — identical
  to old Context behavior. Components should migrate to direct
  useModalStore(selectModalOpen(...)) calls for granular subscriptions.

- Issue #5: Add 14 new tests covering no-op guard behavior (7 tests
  including render count verification), getModalActions() API surface
  and cross-call store sharing (3 tests), and useModalActions()
  reactive state and compatibility (4 tests).

Issues #3 (memory leak) and #4 (type overloads) are not actionable:
47 fixed modal IDs is bounded, and ModalDataFor<T> already resolves
to undefined for unmapped modals.
@claude claude bot mentioned this pull request Feb 7, 2026
claudepalmeragent pushed a commit to claudepalmeragent/Maestro that referenced this pull request Feb 9, 2026
Adds investigation and planning documents for:

1. PRICING-BUGFIXES-PHASE2.md - Summary of 5 issues found during testing:
   - Issue RunMaestro#1: Agent Settings Detection - WORKING CORRECTLY
   - Issue RunMaestro#2: Folder Toggle Shows Blank - Minor bug, fix ready
   - Issue RunMaestro#3: Folder Detection Shows API - Critical bug, fix ready
   - Issue RunMaestro#4: Analysis of RunMaestro#1 vs RunMaestro#3
   - Issue RunMaestro#5: Dashboard costs - Requires separate plan

2. PRICING-DASHBOARD-COST-FIX.md - Comprehensive plan for Issue RunMaestro#5:
   - Root cause: Costs stored at API rates, billing mode never applied
   - Solution: Recalculate at storage time with proper billing mode
   - 6-phase implementation plan with database schema changes
   - Risk assessment and mitigation strategies
   - Timeline estimate: 12-18 hours

Auto Run fix documents created in /app/__AUTORUN/:
- PRICING-FIX-02-FOLDER-TOGGLE.md
- PRICING-FIX-03-FOLDER-DETECTION.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
claudepalmeragent pushed a commit to claudepalmeragent/Maestro that referenced this pull request Feb 9, 2026
…unMaestro#3)

Issue RunMaestro#2 - Folder toggle shows blank:
- Updated calculateProjectBillingState() to check detected modes when all agents are 'auto'
- If all detected modes match, shows that mode instead of 'mixed'

Issue RunMaestro#3 - Folder shows "API Key" instead of "Max":
- Extract SSH remote ID from session.sessionSshRemoteConfig when enabled
- Pass sshRemoteId to detectAuth() call for proper detection
- Added debug logging for verification

Also:
- Archived original pricing enhancement plan
- Updated PRICING-BUGFIXES-PHASE2.md to reflect completed status
- Added 6 new unit tests for SSH remote detection

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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

Comments