Pull button stays enabled with local changes and then fails

[johnmog]

Problem

When there are both local changes and remote commits, the top-left UI shows both Commit and Pull.

In this state, Pull is bright green but cannot succeed because local changes are present.

Why this is confusing

The UI suggests Pull is actionable, but it is effectively guaranteed to fail until local changes are handled.

Suggested fixes

1. Make Pull run an automatic stash -> pull -> pop flow (or expose this via split-button options).
2. Disable/grey out Pull when the working tree is dirty, with a tooltip explaining that local changes must be committed/stashed first.
3. Or another workflow that makes this state succeed predictably instead of failing.

Expected behavior

In the "local changes + remote commits" state, Pull should either:

• succeed via an explicit conflict-safe workflow, or
• be clearly unavailable with guidance on what to do next.

Actual behavior

Pull appears available (bright green) but fails due to local changes.