[QoL] "ERROR: There are uncommitted changes" is too aggressive

Open

#66 opened on Feb 12, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: git, python
Domain: cli, tooling

Research direction

Start by tracing the uncommitted-changes verification used before stack-pr operations, paying particular attention to how modified submodules are reported. Check the relevant tests or command entry points if present; done means submodule-only modifications no longer block operations unnecessarily while genuine uncommitted changes retain their intended handling.

Written by the indexing model from the issue text.

Description

enhancement

Stops all stack-pr operations if submodules have been modified. It's not noticed by any underlying git operation, and seems like excessive verification which does not actually add safety.

Dominant language: Python
Stars: 569
Forks: 43
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.