* Changes from fix/fetch-before-pull-fetch
* feat: Improve pull request flow, add branch selection for worktree creation, fix for automode concurrency count
* feat: Add validation for remote names and improve error handling
* Address PR comments and mobile layout fixes
* ```
refactor: Extract PR target resolution logic into dedicated service
```
* feat: Add app shell UI and improve service imports. Address PR comments
* fix: Improve security validation and cache handling in git operations
* feat: Add GET /list endpoint and improve parameter handling
* chore: Improve validation, accessibility, and error handling across apps
* chore: Format vite server port configuration
* fix: Add error handling for gh pr list command and improve offline fallbacks
* fix: Preserve existing PR creation time and improve remote handling
Add variant prop to Spinner component to support different color contexts:
- 'primary' (default): Uses text-primary for standard backgrounds
- 'foreground': Uses text-primary-foreground for primary backgrounds
- 'muted': Uses text-muted-foreground for subtle contexts
Updated components where spinners were invisible against primary backgrounds:
- TaskProgressPanel: Active task indicators now visible
- Button: Auto-detects spinner variant based on button style
- Various dialogs and setup views using buttons with loaders
Fixes#670🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This update standardizes the loading indicators by replacing all instances of Loader2 with the new Spinner component. The Spinner component provides a consistent look and feel for loading states throughout the UI, enhancing the user experience.
Changes include:
- Updated loading indicators in various components such as popovers, modals, and views.
- Ensured that the Spinner component is used with appropriate sizes for different contexts.
No functional changes were made; this is purely a visual and structural improvement.
The merge handler previously hardcoded branch names as `feature/${featureId}`
and worktree paths as `.worktrees/${featureId}`, which failed for auto-generated
branches (e.g., `feature/v0.11.0rc-1768413895104-31pa`) and custom worktrees.
Changes:
- Server handler now accepts branchName and worktreePath directly from the UI
- Added branch existence validation before attempting merge
- Updated merge dialog with 2-step confirmation (type "merge" to confirm)
- Removed feature branch naming restriction - any branch can now be merged
- Updated API types and client to pass correct parameters
Closes#408
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
