Hive Pull Requests

Hive Pull Requests

Create a GitHub pull request and attach the branch to the relevant Hive action when GitHub tooling is available.

Workflow

1. Gather branch and repo context.

   • Run git status, recent log, and diff from the branch base.
   • Determine current branch, origin repo, upstream, and target base branch.
   • If there are uncommitted changes, ask whether to commit first.

2. Push the branch if needed.

   • If there is no upstream, push with git push -u origin HEAD.

3. Create the pull request.

   • Use gh or available GitHub tooling.
   • Derive title from branch or commits.
   • Build a concise body from branch diff and user context.
   • Include a Hive action link when an action is known.

4. Resolve the Hive action.

   • Use the action URL/ID/title from conversation context if unambiguous.
   • If ambiguous, ask which Hive action to attach.
   • Confirm the action exists via Hive MCP before updating it.

5. Attach the branch.

   • Use Hive MCP updateActionGithubBranchNames when available.
   • Preserve existing branch links unless the workspace-specific convention says to normalize them.
   • Use the repository and branch format expected by the Hive workspace.

6. Confirm outcome with the PR URL and Hive action link.

Never commit directly to protected target branches. Always use PRs.