Define gating policy for local git picker actions #184

New issue

Closed

opened 2026-04-12 19:29:29 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-04-12 19:29:29 +00:00

Problem

The local git pickers for branches, commits, and worktrees expose actions, but there is no explicit cross-surface policy for when those actions should appear or be suppressed.

Examples include delete actions that are blocked only after selection, worktree actions that depend on current location or checked-out state, and branch/commit actions whose availability is partly implied rather than defined.

Expected

Define a consistent gating policy across the local git picker surfaces.

That should cover at least:

branch delete visibility vs. post-selection rejection
worktree delete/add/switch visibility when the target is current or otherwise invalid
commit and branch browse/copy/show action consistency
whether invalid actions are hidden or disabled across these local pickers

Notes

This is about picker-surface consistency for local git objects, not forge-hosted PR/issue/release actions.

## Problem The local git pickers for branches, commits, and worktrees expose actions, but there is no explicit cross-surface policy for when those actions should appear or be suppressed. Examples include delete actions that are blocked only after selection, worktree actions that depend on current location or checked-out state, and branch/commit actions whose availability is partly implied rather than defined. ## Expected Define a consistent gating policy across the local git picker surfaces. That should cover at least: - branch delete visibility vs. post-selection rejection - worktree delete/add/switch visibility when the target is current or otherwise invalid - commit and branch browse/copy/show action consistency - whether invalid actions are hidden or disabled across these local pickers ## Notes This is about picker-surface consistency for local git objects, not forge-hosted PR/issue/release actions.

barrettruth commented

2026-04-12 21:39:28 +00:00

Closing this because the product direction is to keep picker actions flat rather than introduce cross-surface local-git action gating. Any remaining local picker UX problems should be tracked as narrower branch, commit, or worktree behavior bugs instead.