workspace-branch

# Workspace & Branch Management All Honeydew MCP tool calls operate against a workspace and branch set for the current session. Use this skill to set up that context, manage branches, and create pull requests when development work is ready for review. --- ## Session Setup (Required Before Any Work) **Step 1: Check existing context** Call `get_session_workspace_and_branch` first. If a workspace and branch are already set, skip to Step 3. **Step 2: Select workspace and branch** ``` list_workspaces → pick a workspace → set_session_workspace_and_branch ``` If the user needs a specific branch, call `list_workspace_branches` first to see available options. **Step 3: For development work, create a branch** ``` create_workspace_branch → session switches automatically ``` Never make modeling changes on the `prod` branch directly. Always create a development branch first. --- ## MCP Tools Reference ### Read-Only Tools - `list_workspaces` — List all available workspaces. Returns the workspace name and data warehouse type (`snowflake`, `databricks`, or `bigquery`). Use the warehouse type to inform SQL dialect choices. - `list_workspace_branches` — List all branches available for a workspace. Requires `workspace_id`. - `get_session_workspace_and_branch` — Get the workspace and branch set for the current session. - `get_branch_history` — Get the change history for the current session's branch. Returns a chronological list of what semantic objects were modified, by whom, and ...