git-worktrees 0.1.0__py3-none-any.whl

git_worktrees-0.1.0.dist-info/METADATA

@@ -0,0 +1,335 @@
+Metadata-Version: 2.5
+Name: git-worktrees
+Version: 0.1.0
+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
+Author-email: Mihai Bojin <557584+MihaiBojin@users.noreply.github.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: cli,git,worktree
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: pre-commit==4.6.1; extra == 'dev'
+Requires-Dist: pytest==9.1.1; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# worktrees
+
+Eight commands. Four of them answer a question and print it; four land you
+somewhere, and those need ten lines of shell each, because a binary cannot
+change its caller's directory.
+
+| | |
+| --- | --- |
+| `gw` | the CLI itself, taking a subcommand. `worktrees` is the same program under its long name |
+| `gws` | say which worktrees are finished, and why. Removes nothing, and has no flag that could |
+| `gwp` | remove the ones `gws` marks removable, having asked first |
+| `gwa NAME [BASE]` | create a worktree for `NAME` and land you in it |
+| `gwl [QUERY]` | pick one of this repository's worktrees and land you in it |
+| `gwm NEW` | rename this worktree's branch and move the checkout to match |
+| `gwr [QUERY]` | remove a worktree whose branch is finished, and the branch |
+| `gwnb NAME` | alpha. Fetch, then branch `NAME` off the head branch and check it out |
+| `gwrot` | alpha. Start the next branch after this one, or catch the head branch up |
+
+`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
+worktrees, which is a different job from the one this repository exists to do,
+and `origin new-branch` and `origin rotate` already do it. Only one of the two
+sets survives. Until that is decided the names, the flags and the output may
+change, and nothing should be built on top of them.
+
+## Install
+
+```console
+uv tool install git+https://github.com/MihaiBojin/worktrees
+```
+
+One venv of 124 KB serves every command name, at about 1 KB each, all of them
+into `~/.local/bin`. A tag installs that release and nothing later:
+
+```console
+uv tool install git+https://github.com/MihaiBojin/worktrees@v0.1.0
+```
+
+Python 3.11 or newer, and no dependencies. The standard library answers every
+question this asks, so an invocation pays for the interpreter and nothing
+else.
+
+Shell functions and completions arrive separately, through a plugin manager,
+the same way any other plugin does. Nothing here ships shell code yet; when
+it does, Fisher reads `functions/`, `completions/` and `conf.d/` from the
+repository root and Antidote takes a `path:` into it:
+
+```console
+fisher install MihaiBojin/worktrees
+```
+
+```
+MihaiBojin/worktrees path:zsh/plugins/worktrees   # in zsh_plugins.txt
+```
+
+Neither manager puts a binary on `$PATH`, which is why the two installs stay
+separate.
+
+## gws
+
+```console
+$ gws
+VERDICT  BRANCH         WHY
+remove   squash-merged  squash-merged
+keep     dirty-work     it has uncommitted changes
+keep     holds-secrets  merged, but holds 2 ignored path(s); pass --delete-ignored
+unknown  never-pushed   not merged into main, and no upstream says whether its commits were pushed
+
+1 removable, 2 kept, 1 unclear
+```
+
+### Three verdicts
+
+Each is the instruction it gives. `unknown` is not `keep` with a softer
+word.
+
+| | means |
+| --- | --- |
+| `remove` | finished, and safe to remove. The reason says how it was proved: `merged`, `squash-merged`, or a ref reaching a detached commit |
+| `keep` | something says no. Uncommitted work, the head branch, a lock, the worktree you are standing in, ignored files, or a branch simply not merged |
+| `unknown` | it could not tell. A branch with no upstream is the usual one: nothing says whether its commits were pushed anywhere |
+
+Where git cannot tell, the forge is asked. A branch merged as part of a
+stack is that case: its changes reach the head branch across several
+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.
+
+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`,
+which mutates, so `gwp` is what runs it.
+
+### Two holes in git
+
+**A squash merge inverts `git branch -d`.** A branch whose change is already in
+`main` reports `error: the branch 'x' is not fully merged` and points you at
+`-D`, which deletes anything. By hand, `squashed` and `unmerged` are
+indistinguishable: both report NOT merged, both sit one commit ahead. Opposite
+correct actions, no signal between them.
+
+The probe that separates them replays the branch's tree as one commit on the
+merge base and asks `git cherry` whether that patch is already upstream. It
+compares content rather than history, which is what a squash preserves.
+
+**`git worktree remove` silently deletes ignored files.** With `.env` and
+`node_modules/` present, `git status --porcelain` prints nothing,
+`git worktree remove` exits 0 with no `--force`, and both are gone. Nothing in
+git brings them back: no ref ever pointed at them. `gws` reads
+`--ignored=traditional`, counts what would go, and marks the worktree `keep`
+until you pass `--delete-ignored`.
+
+## gwp
+
+```console
+$ gwp
+squash-merged  ~/git/.worktrees/squash-merged/repo
+  restore with: git branch squash-merged d79e417
+remove 1 worktree(s)? [y/N]
+```
+
+It removes exactly the rows `gws` marks `remove`, under the same flags, and one
+function returns that set for both. What goes and what puts it back is printed
+before anything does, and neither `--quiet` nor `--yes` silences it.
+
+`-y` skips the question. A run whose stdin is not a terminal refuses rather
+than blocking, because an agent or a pipe reaching a prompt would hang forever
+holding the repository's worktrees:
+
+```console
+$ gwp < /dev/null
+not a terminal, so nothing can answer for the 1 above; pass --yes to remove them
+```
+
+The checkout goes through plain `git worktree remove`, so every refusal git
+makes still applies. The branch goes through `git branch -d`, never `-D`, so a
+squash-merged branch keeps its ref after its worktree is gone.
+
+There is no `--dry-run`. `gws` reports and `gwp` asks, so a flag meaning "do
+not act" would be a no-op wearing the clothes of a safety feature, and somebody
+would one day cite it as the reason a sweep was safe.
+
+## gwnb (alpha)
+
+```console
+$ gwnb fix-parser
+fix-parser from origin/main at 4a91c02
+```
+
+Alpha, and a branch command rather than a worktree one. See the note above
+the install section.
+
+The base is `<remote>/<head>` as it stands after the fetch, not the local copy
+of it, so the branch starts on top of what the server has and nothing has to be
+rebased afterwards. It travels as a full ref, because git resolves a bare name
+as a tag first and a repository holding a tag called `origin/main` would branch
+from the tag.
+
+`--no-track`, so the head branch does not become the new branch's upstream. A
+branch that tracked it would take it as its upstream and `git push` would
+target the head branch.
+
+A failed fetch is not fatal. An offline machine still gets a branch, off
+whatever it last saw, and the line at the end names the commit it got.
+
+## gwrot (alpha)
+
+```console
+$ gwrot
+fix-parser-2026-09-11_001 from origin/main at 4a91c02
+```
+
+Alpha, on the same footing as `gwnb`.
+
+It takes no argument. The name comes from the branch you are standing on,
+with any suffix a previous rotation added already stripped, so four
+rotations in a day give four siblings rather than one name carrying four
+suffixes:
+
+```
+fix-parser                   -> fix-parser-2026-09-11_001
+fix-parser-2026-09-11_001    -> fix-parser-2026-09-11_002
+fix-parser-2026-09-10_003    -> fix-parser-2026-09-11_001
+```
+
+Three digits, so the sequence cannot be read as another field of the date. A
+number is free only when neither `refs/heads/` nor the remote holds it, or
+two people rotate into the same name.
+
+On the head branch there is no chain to continue, so it catches that up
+instead:
+
+```console
+$ gwrot
+main is at origin/main
+```
+
+That is `merge --ff-only`, never a rebase: rewriting local commits on the
+head branch is the class this tooling refuses everywhere else. Commits the
+remote does not have are refused and listed, because they are a change of
+their own and `gwnb` puts them on a branch.
+
+## gwa, gwl, gwm, gwr
+
+Worktrees live at `<PARENT>/.worktrees/<NAME>/<REPO>`, derived rather than
+configured, so two tools cannot disagree about a location neither can be
+told. A branch name with slashes becomes directories, and the repository
+name goes last, so `feat/oauth` cannot collide with `feat`.
+
+```console
+$ gwa fix-parser          # creates it and lands you in it
+$ gwl parse               # one match takes it outright
+$ gwm parser-v2           # renames the branch and moves the checkout
+$ gwr                     # removes the one you are standing in
+```
+
+Each prints one destination on stdout and nothing else, which is what the
+shell function reads. `gwr` prints a path **only** when you were standing in
+what it removed; empty output means stay put.
+
+`gwm` is the one that is not a convenience. Renaming the directory you are
+standing in leaves the shell with a stale `$PWD` and every later command
+failing:
+
+```console
+$ git status
+fatal: Unable to read current working directory: No such file or directory
+```
+
+`gwl` with more than one match asks, numbered. Matching is substring first
+and then subsequence, so `tst` finds `add-tests`, and a substring hit always
+outranks a loose one. Without a terminal it refuses rather than blocking and
+names `--list` and `--json`.
+
+`gwr` refuses a branch that is not finished and says why, the same verdict
+`gws` prints. `--force` removes the checkout and keeps the branch: the
+worktree was in the way, the work was not.
+
+## Flags
+
+`--branch NAME`, `--no-fetch`, `--delete-ignored`, `--json`, `-q`, `-v` and
+`--explain` are shared by `gws` and `gwp`. `-y` is `gwp` alone. `gwnb` and
+`gwrot` take `--no-fetch`, `--json`, `-q`, `-v` and `--explain`.
+
+Data goes to stdout and diagnostics to stderr, including the prompt, so
+`--json` is parseable in every mode.
+
+## From a prompt, and from a script
+
+Every command here is a console script, so a script reaches it with no shell
+loaded at all. `gws` and `gwnb` answer identically either way:
+
+```console
+$ gws --json | jq -r '.verdicts[] | select(.verdict=="remove") | .branch'
+fix-parser
+
+$ fish -c 'gws --json' | jq '.verdicts | length'
+4
+
+$ bash -c 'gwnb spike --json' | jq -r .base
+refs/remotes/origin/main
+```
+
+`gwp` is the one that reads the terminal, and it does so deliberately. With a
+tty it asks; without one it refuses rather than blocking, because a script or
+an agent reaching a prompt would hang holding the repository's worktrees:
+
+```console
+$ gwp                       # at a prompt
+squash-merged  ~/git/.worktrees/squash-merged/repo
+  restore with: git branch squash-merged d79e417
+remove 1 worktree(s)? [y/N] y
+removed 1 worktree(s)
+
+$ gwp < /dev/null           # in a script, a pipe, a CI job
+not a terminal, so nothing can answer for the 1 above; pass --yes to remove them
+
+$ gwp --yes --json          # what an agent runs
+{"removed": ["squash-merged"], "failed": 0}
+```
+
+Data is on stdout and every diagnostic on stderr, the prompt included, so
+`--json` parses in all three cases.
+
+## What it refuses
+
+Six git commands are refused wherever they appear, whatever flags are passed
+and whatever a caller asks for:
+
+```
+reset --hard      a forced checkout or switch      clean -f
+push --force      worktree remove --force          branch -D
+```
+
+The check runs on the argument list as it is about to be handed to git, so no
+code path can assemble its way past one. `gws --explain` prints every git
+command the program can issue, all 28 of them, marking the six that change
+anything.
+
+`--force-with-lease` is not `--force` and is allowed. `branch -d` is not
+`branch -D` and is how a branch is deleted here: on git's own proof of merge,
+or not at all.
+
+## Contributing
+
+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).

git_worktrees-0.1.0.dist-info/RECORD

@@ -0,0 +1,18 @@
+worktrees/__init__.py,sha256=NHzb254l9gQY31NSEkRoeL2tSpMj0J_-jLzaQwcUDAs,263
+worktrees/cli.py,sha256=c5AIhGLqYgeHm76CXQ-mTaZ2wouB-znn_1WnMeItFZM,24457
+worktrees/forge.py,sha256=1h7Dx37wd1IzR20XtFDx6j7czeYzWck8cj2u_LaG4qk,2896
+worktrees/git.py,sha256=7ZXyJQof-Jp0s7MWN5Wq8Nz0bEpMdR4dr_kWKtjQGQc,9588
+worktrees/layout.py,sha256=9p3fHRhvVKSkLvoyiPAsT35MoytTffKjikqPyta8-Do,1793
+worktrees/merged.py,sha256=UWs6Gyj6zFXQQLwS4fUwMgYYdb1VbimXBCzhH114uio,3393
+worktrees/new_branch.py,sha256=aDn5NMviZo_Kr1GEPWNFmfDPzdMMEY3BWbr5LZWbTvk,2588
+worktrees/pick.py,sha256=CD97wJ9N0EiMi6ak58i4sGgPoZWEH1lX7RaCtJ3G5eg,3642
+worktrees/prune.py,sha256=8AsbnmGVpea3lINg8w92APhQHycV_VGKQyZjOjVlf4s,5327
+worktrees/repo.py,sha256=I3ENTjOHulo2cRdAKpYa2uhZ6TXYrQbbGSmQdBsHAhQ,11217
+worktrees/rotate.py,sha256=-zw_0qNp1IC_XK--NsWiZzPK8fMpX54reo3VLmH3BuY,4727
+worktrees/verdicts.py,sha256=thhS5Q02ZLm0TYCa_Yw94RdTPJ-3r4jfuc8XGRLW4OA,5328
+worktrees/worktree.py,sha256=BgS4IjJFyXghNwThyjKWIQF2PB0ZJ1EpvTPqxtIcpts,7276
+git_worktrees-0.1.0.dist-info/METADATA,sha256=97A7sf0PVv1U5jhJCAVEelSQQlVRsFU5vXe0jptPlN4,12967
+git_worktrees-0.1.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+git_worktrees-0.1.0.dist-info/entry_points.txt,sha256=6pGH1pmMRQB3PFhZrOFRpzq3mku4azrqIquLFLhsJyc,271
+git_worktrees-0.1.0.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
+git_worktrees-0.1.0.dist-info/RECORD,,

git_worktrees-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.0
+Root-Is-Purelib: true
+Tag: py3-none-any

git_worktrees-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,11 @@
+[console_scripts]
+gw = worktrees.cli:main
+gwa = worktrees.cli:gwa
+gwl = worktrees.cli:gwl
+gwm = worktrees.cli:gwm
+gwnb = worktrees.cli:gwnb
+gwp = worktrees.cli:gwp
+gwr = worktrees.cli:gwr
+gwrot = worktrees.cli:gwrot
+gws = worktrees.cli:gws
+worktrees = worktrees.cli:main

git_worktrees-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

worktrees/__init__.py

@@ -0,0 +1,8 @@
+"""Git worktree commands that refuse to lose work."""
+
+from importlib.metadata import PackageNotFoundError, version
+
+try:
+    __version__ = version("git-worktrees")
+except PackageNotFoundError:  # a source tree nothing has installed
+    __version__ = "0+unknown"