git-worktrees 0.3.1__tar.gz → 0.4.1__tar.gz

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/.github/workflows/publish.yml

@@ -36,7 +36,7 @@ jobs:
   # byte-for-byte what was tested and installed here.
   build:
     name: Build
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     permissions:
       contents: read
       # Reading another workflow's runs. Without it the tests guard below
@@ -56,6 +56,7 @@ jobs:
         with:
           python-version: "3.14"
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       - name: Install the release tools
         uses: releasetools/cli@v0
@@ -126,7 +127,7 @@ jobs:
 
   publish:
     name: Publish to PyPI
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     needs: build
     # Binds this job to the trusted publisher registered for `pypi`. Add a
     # required reviewer on this environment for a manual gate before anything
@@ -144,6 +145,7 @@ jobs:
         with:
           python-version: "3.14"
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       - name: Download distributions
         uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8
@@ -162,7 +164,7 @@ jobs:
   # PyPI is slow rather than that the version is not out.
   verify:
     name: Verify it installs from PyPI
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     needs: publish
     permissions:
       contents: read
@@ -178,13 +180,14 @@ jobs:
         with:
           python-version: "3.14"
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       - name: Verify it installs from PyPI
         run: scripts/verify-publish.bash --prod
 
   release:
     name: Release
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     needs: publish
     permissions:
       contents: write

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/.github/workflows/testpypi.yml

@@ -28,7 +28,7 @@ permissions:
 jobs:
   snapshot:
     name: Publish a snapshot
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     # Binds this job to the trusted publisher registered for `testpypi`.
     environment: testpypi
     permissions:
@@ -47,6 +47,7 @@ jobs:
         with:
           python-version: "3.14"
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       # Epoch seconds rather than the run number: a re-run repeats the number
       # and TestPyPI refuses the duplicate, while the clock has moved on.

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/.github/workflows/tests.yml

@@ -23,7 +23,7 @@ concurrency:
 jobs:
   lint:
     name: Lint
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     steps:
       - name: Checkout code
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
@@ -33,6 +33,7 @@ jobs:
         with:
           python-version: "3.14"
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       - name: Install dependencies
         run: uv sync --all-extras --locked
@@ -44,7 +45,7 @@ jobs:
 
   test:
     name: Python ${{ matrix.python-version }}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     strategy:
       # One version failing is a fact about that version, so let the others
       # finish and say which.
@@ -66,6 +67,7 @@ jobs:
         with:
           python-version: ${{ matrix.python-version }}
           enable-cache: true
+          cache-suffix: ${{ github.workflow }}-${{ github.job }}
 
       - name: Install dependencies
         # --locked fails the run on a stale uv.lock, rather than quietly

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/CHANGELOG.md

@@ -17,6 +17,37 @@ not in here, whatever it cost to build.
 A release closes with a `### Choices` section when a decision in it is worth
 the reader's time: what was chosen, and what the alternative failed to do.
 
+## 0.4.1 - 2026-09-21
+
+CLI behavior is unchanged from 0.4.0.
+
+## 0.4.0 - 2026-09-21
+
+### Security
+
+Forge queries ignore `GH_REPO` and `GITLAB_REPO`, so a merged request in
+another repository cannot authorize removal here.
+
+Printed branch restoration commands and `gwnb` checkout hints quote branch
+names so shell metacharacters are treated as part of the name.
+
+### Added
+
+`gws` reports how many worktrees under the shared `.worktrees` directory
+belong to other repositories, with the count in `gws --json` as `neighbours`.
+
+### Fixed
+
+After a failed fetch, worktree assessments use local refs and skip forge
+queries.
+
+`gwl` and `gwr` shell completions omit paths containing newlines, which
+cannot fit their one-row-per-line format; those worktrees remain reachable
+by name or path.
+
+Pressing Ctrl-C at a worktree selection or removal prompt exits with code
+130 and no traceback. No worktree is selected or removed.
+
 ## 0.3.1 - 2026-09-20
 
 `gws` and `gwp` list the main checkout, and `gwl`'s picker shows the

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: git-worktrees
-Version: 0.3.1
+Version: 0.4.1
 Summary: Git worktree commands that refuse to lose work.
 Project-URL: Bug reports, https://github.com/MihaiBojin/worktrees/issues/new
 Project-URL: Source, https://github.com/MihaiBojin/worktrees
@@ -64,6 +64,10 @@ function, because a binary cannot change its caller's directory.
 
 `worktrees` is the same program under its long name.
 
+Ctrl-C interrupts a running command with exit code 130 and no traceback.
+At a selection or removal prompt, it cancels without choosing or removing
+a worktree.
+
 `gws` and `gwp` are what this tool is for and their behaviour is settled.
 
 **`gwnb` and `gwrot` are alpha and may go.** They start branches rather than
@@ -160,6 +164,12 @@ subcommand and shorthand, `gwl --complete` prints every worktree, and both
 shells narrow what those return, so the matching stays in one place and a
 command added to the table needs no edit in either shell.
 
+One row a line, `label<TAB>path`. A worktree whose path holds a newline is
+left out of that listing, because both shells would read it as two rows and
+offer the tail as a worktree of its own. `gwa` cannot make such a path, since
+it derives from a branch name and git refuses a newline in a ref, and the
+worktree is still reachable by name or path.
+
 Neither manager puts a binary on `$PATH`, which is why the two installs stay
 separate.
 
@@ -175,6 +185,7 @@ unknown  never-pushed   not merged into origin/main, and no upstream says whethe
 remove   squash-merged  squash-merged                                                                      /home/you/git/.worktrees/squash-merged/repo
 
 1 removable, 3 kept, 1 unclear
+2 worktree(s) under /home/you/git/.worktrees belong to another repository
 unclear, and gwp does not touch these: never-pushed
 gwp removes the 1 marked removable
 ```
@@ -184,7 +195,13 @@ so the table shows what `git worktree list` shows; nothing proposes it, and
 `git worktree remove` answers `fatal: '<path>' is a main working tree`
 whatever flag it is given. Paths are absolute wherever this
 prints one, so a row can be pasted into the next command. The table and the
-count are on stdout; the two lines after them are on stderr.
+count are on stdout; everything after them is on stderr.
+
+Every repository in the same parent directory keeps its worktrees under that
+one `.worktrees` root, so some of the directories in there are a sibling's.
+`gws` counts those and says so, because nothing else does, and `--json`
+carries the same count as `neighbours`. No command here reads or removes
+them, and the count comes from walking the root rather than from asking git.
 
 On a terminal the verdict carries its own colour, `remove` green, `keep` blue
 and `unknown` yellow, with the branch in bold and the path dimmed. That
@@ -208,7 +225,13 @@ squashes, so the intermediate state it holds differs from the final one in
 the same regions, and a diff cannot separate a stale branch from one with
 work left. A merged pull request settles it, cross-checked against the
 commits an upstream has not got, because a request speaks for what reached
-it and nothing about what never did. `--no-forge` decides from git alone.
+it and nothing about what never did. `--no-forge` decides from git alone, and
+so does a run whose fetch just failed.
+
+The question goes to the repository the command is standing in and nowhere
+else. `GH_REPO` and `GITLAB_REPO` beat that directory, so both are dropped
+before `gh` or `glab` runs; everything else in the environment, the token
+included, is passed through.
 
 A record left behind by a directory somebody deleted by hand is nobody's
 verdict. `gws` names how many there are; clearing them is `git worktree prune`,
@@ -452,7 +475,10 @@ print one thing each and have nothing to be quiet about, takes `--json`, `-q`,
 
 A remote that cannot be reached is not fatal anywhere. The fetch fails, the
 command says so on stderr, and it answers from the refs already here, which is
-where `--no-fetch` sends it on request.
+where `--no-fetch` sends it on request. The forge is not asked either: it is
+over the same network, and `gh` waits 30 seconds before saying so, once per
+branch. `--no-fetch` alone says nothing about the network, so it leaves the
+forge asked.
 
 Data goes to stdout and diagnostics to stderr, the prompt included, so `--json`
 is parseable in every mode. Colour is decided per stream and only for a
@@ -507,7 +533,9 @@ is refused with them: it deletes refs without `-d` appearing at all.
 The Python, the tests and the release procedure are in
 [docs/DEVELOPMENT.md](docs/DEVELOPMENT.md). The rules the code follows are in
 [AGENTS.md](AGENTS.md). What changed in each release is in
-[CHANGELOG.md](CHANGELOG.md).
+[CHANGELOG.md](CHANGELOG.md). What was decided and what must not break,
+including the alternatives that were closed, is in
+[docs/REFERENCE.md](docs/REFERENCE.md).
 
 ## Licence
 

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/README.md

@@ -38,6 +38,10 @@ function, because a binary cannot change its caller's directory.
 
 `worktrees` is the same program under its long name.
 
+Ctrl-C interrupts a running command with exit code 130 and no traceback.
+At a selection or removal prompt, it cancels without choosing or removing
+a worktree.
+
 `gws` and `gwp` are what this tool is for and their behaviour is settled.
 
 **`gwnb` and `gwrot` are alpha and may go.** They start branches rather than
@@ -134,6 +138,12 @@ subcommand and shorthand, `gwl --complete` prints every worktree, and both
 shells narrow what those return, so the matching stays in one place and a
 command added to the table needs no edit in either shell.
 
+One row a line, `label<TAB>path`. A worktree whose path holds a newline is
+left out of that listing, because both shells would read it as two rows and
+offer the tail as a worktree of its own. `gwa` cannot make such a path, since
+it derives from a branch name and git refuses a newline in a ref, and the
+worktree is still reachable by name or path.
+
 Neither manager puts a binary on `$PATH`, which is why the two installs stay
 separate.
 
@@ -149,6 +159,7 @@ unknown  never-pushed   not merged into origin/main, and no upstream says whethe
 remove   squash-merged  squash-merged                                                                      /home/you/git/.worktrees/squash-merged/repo
 
 1 removable, 3 kept, 1 unclear
+2 worktree(s) under /home/you/git/.worktrees belong to another repository
 unclear, and gwp does not touch these: never-pushed
 gwp removes the 1 marked removable
 ```
@@ -158,7 +169,13 @@ so the table shows what `git worktree list` shows; nothing proposes it, and
 `git worktree remove` answers `fatal: '<path>' is a main working tree`
 whatever flag it is given. Paths are absolute wherever this
 prints one, so a row can be pasted into the next command. The table and the
-count are on stdout; the two lines after them are on stderr.
+count are on stdout; everything after them is on stderr.
+
+Every repository in the same parent directory keeps its worktrees under that
+one `.worktrees` root, so some of the directories in there are a sibling's.
+`gws` counts those and says so, because nothing else does, and `--json`
+carries the same count as `neighbours`. No command here reads or removes
+them, and the count comes from walking the root rather than from asking git.
 
 On a terminal the verdict carries its own colour, `remove` green, `keep` blue
 and `unknown` yellow, with the branch in bold and the path dimmed. That
@@ -182,7 +199,13 @@ squashes, so the intermediate state it holds differs from the final one in
 the same regions, and a diff cannot separate a stale branch from one with
 work left. A merged pull request settles it, cross-checked against the
 commits an upstream has not got, because a request speaks for what reached
-it and nothing about what never did. `--no-forge` decides from git alone.
+it and nothing about what never did. `--no-forge` decides from git alone, and
+so does a run whose fetch just failed.
+
+The question goes to the repository the command is standing in and nowhere
+else. `GH_REPO` and `GITLAB_REPO` beat that directory, so both are dropped
+before `gh` or `glab` runs; everything else in the environment, the token
+included, is passed through.
 
 A record left behind by a directory somebody deleted by hand is nobody's
 verdict. `gws` names how many there are; clearing them is `git worktree prune`,
@@ -426,7 +449,10 @@ print one thing each and have nothing to be quiet about, takes `--json`, `-q`,
 
 A remote that cannot be reached is not fatal anywhere. The fetch fails, the
 command says so on stderr, and it answers from the refs already here, which is
-where `--no-fetch` sends it on request.
+where `--no-fetch` sends it on request. The forge is not asked either: it is
+over the same network, and `gh` waits 30 seconds before saying so, once per
+branch. `--no-fetch` alone says nothing about the network, so it leaves the
+forge asked.
 
 Data goes to stdout and diagnostics to stderr, the prompt included, so `--json`
 is parseable in every mode. Colour is decided per stream and only for a
@@ -481,7 +507,9 @@ is refused with them: it deletes refs without `-d` appearing at all.
 The Python, the tests and the release procedure are in
 [docs/DEVELOPMENT.md](docs/DEVELOPMENT.md). The rules the code follows are in
 [AGENTS.md](AGENTS.md). What changed in each release is in
-[CHANGELOG.md](CHANGELOG.md).
+[CHANGELOG.md](CHANGELOG.md). What was decided and what must not break,
+including the alternatives that were closed, is in
+[docs/REFERENCE.md](docs/REFERENCE.md).
 
 ## Licence
 

{git_worktrees-0.3.1 → git_worktrees-0.4.1}/docs/DEVELOPMENT.md

@@ -24,7 +24,9 @@ invisible to it, so CI is the first thing to format a file you just wrote.
 
 
 The rules this code follows, and the reasoning behind them, are in
-[AGENTS.md](../AGENTS.md). This file is what to run.
+[AGENTS.md](../AGENTS.md). What was decided, what must not break and which
+failure classes have a test are in [REFERENCE.md](REFERENCE.md). This file is
+what to run.
 
 ## Layout