Alex Netsch 4c7e35899d Fix dropdown (vibe-kanban) (#764)
* Perfect! I have successfully fixed the dropdown actions issue in the non-fullscreen mode. Here's a summary of what was implemented:

##  Fixed Dropdown Actions in Non-Fullscreen Mode

### **Problem Solved**
The dropdown in task attempt details (non-fullscreen mode) was always showing "Rebase" and "Merge" actions, regardless of the branch status conditions. This was inconsistent with the fullscreen mode which properly applied conditional logic.

### **Changes Made**

1. **Added Required Imports** (`AttemptHeaderCard.tsx:16-18`):
   - `useBranchStatus` hook for branch status information
   - `useAttemptExecution` hook for execution state
   - `useMemo` and `useState` for state management

2. **Added Branch Status Logic** (`AttemptHeaderCard.tsx:52-97`):
   - Branch status data fetching
   - Conflict detection
   - Merge status information (open PRs, merged PRs, etc.)
   - Loading states for rebase and merge operations

3. **Enhanced Action Handlers** (`AttemptHeaderCard.tsx:109-129`):
   - Added proper async handlers with loading states
   - Proper error handling through mutations

4. **Applied Conditional Rendering**:
   - **Rebase** (`AttemptHeaderCard.tsx:186-193`): Only shown when:
     - Branch has commits behind (needs rebasing)
     - No merged PR exists
     - Branch status is available
   - **Merge** (`AttemptHeaderCard.tsx:200-214`): Only shown when:
     - No open PR exists
     - No conflicts present
     - Branch is not behind (rebased)
     - Has commits ahead to merge
     - No merged PR exists
     - Attempt is not running

### **Result**
Now both fullscreen and non-fullscreen modes apply the same conditional logic for rebase and merge actions, providing a consistent user experience. The dropdown will only show these actions when they are actually applicable based on the branch status.

 **All linting and formatting checks passed** (99 warnings, 0 errors - warnings are acceptable).

* fmt
2025-09-18 12:08:52 +01:00
2025-08-08 13:53:27 +01:00
2025-09-18 08:15:05 +00:00
2025-08-08 13:53:27 +01:00
2025-09-18 11:17:56 +01:00
2025-09-18 08:15:05 +00:00
2025-09-04 10:52:18 +01:00
2025-09-04 15:11:41 +01:00
2025-08-08 13:53:27 +01:00
2025-08-08 13:53:27 +01:00
2025-07-11 15:57:30 +01:00
2025-09-04 10:52:18 +01:00
2025-07-11 16:31:08 +01:00
2025-09-18 08:15:05 +00:00
2025-06-14 15:14:08 -04:00
2025-06-25 09:27:29 +01:00
2025-06-25 09:27:29 +01:00
2025-07-04 11:11:45 +02:00

Vibe Kanban Logo

Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...

npm Build status Ask DeepWiki

Overview

AI coding agents are increasingly writing the world's code and human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks. Vibe Kanban streamlines this process, enabling you to:

  • Easily switch between different coding agents
  • Orchestrate the execution of multiple coding agents in parallel or in sequence
  • Quickly review work and start dev servers
  • Track the status of tasks that your coding agents are working on
  • Centralise configuration of coding agent MCP configs

You can watch a video overview here.

Installation

Make sure you have authenticated with your favourite coding agent. A full list of supported coding agents can be found in the docs. Then in your terminal run:

npx vibe-kanban

Documentation

Please head to the website for the latest documentation and user guides.

Support

Please open an issue on this repo if you find any bugs or have any feature requests.

Contributing

We would prefer that ideas and changes are raised with the core team via GitHub issues, where we can discuss implementation details and alignment with the existing roadmap. Please do not open PRs without first discussing your proposal with the team.

Development

Prerequisites

Additional development tools:

cargo install cargo-watch
cargo install sqlx-cli

Install dependencies:

pnpm i

Running the dev server

pnpm run dev

This will start the frontend and backend with live reloading. A blank DB will be copied from the dev_assets_seed folder.

Build from source

  1. Run build-npm-package.sh
  2. In the npx-cli folder run npm pack
  3. You can run your build with npx [GENERATED FILE].tgz

Environment Variables

The following environment variables can be configured at build time or runtime:

Variable Type Default Description
GITHUB_CLIENT_ID Build-time Ov23li9bxz3kKfPOIsGm GitHub OAuth app client ID for authentication
POSTHOG_API_KEY Build-time Empty PostHog analytics API key (disables analytics if empty)
POSTHOG_API_ENDPOINT Build-time Empty PostHog analytics endpoint (disables analytics if empty)
BACKEND_PORT Runtime 0 (auto-assign) Backend server port
FRONTEND_PORT Runtime 3000 Frontend development server port
HOST Runtime 127.0.0.1 Backend server host
DISABLE_WORKTREE_ORPHAN_CLEANUP Runtime Not set Disable git worktree cleanup (for debugging)

Build-time variables must be set when running pnpm run build. Runtime variables are read when the application starts.

Custom GitHub OAuth App (Optional)

By default, Vibe Kanban uses Bloop AI's GitHub OAuth app for authentication. To use your own GitHub app for self-hosting or custom branding:

  1. Create a GitHub OAuth App at GitHub Developer Settings
  2. Enable "Device Flow" in the app settings
  3. Set scopes to include user:email,repo
  4. Build with your client ID:
    GITHUB_CLIENT_ID=your_client_id_here pnpm run build
    
Description
Get 10X more out of Claude Code, Codex or any coding agent
https://www.vibekanban.com/
Readme Apache-2.0 48 MiB
Languages
Rust 51.1%
TypeScript 46.6%
CSS 1.1%
JavaScript 0.7%
PLpgSQL 0.2%
Other 0.2%