copierz 0.1.0__tar.gz

copierz-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

copierz-0.1.0/PKG-INFO

@@ -0,0 +1,181 @@
+Metadata-Version: 2.4
+Name: copierz
+Version: 0.1.0
+Summary: CLI to track and apply Copier updates across a fleet of git repositories.
+Author: m09
+Author-email: m09 <142691+m09@users.noreply.github.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Dist: copier>=9.9,<10
+Requires-Dist: packaging>=24
+Requires-Dist: pyyaml>=6,<7
+Requires-Dist: rich>=13
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+
+# `copierz`
+
+A CLI to track the git repos — and every branch of them — generated from
+[Copier](https://copier.readthedocs.io/) templates, see which are behind
+their template, and bring them up to date in one go.
+
+## Configuring
+
+copierz reads `~/.config/copierz/config.toml` (or `$XDG_CONFIG_HOME`, or
+`--config PATH`):
+
+```toml
+# Scanned recursively on every run.
+roots = ["~/repos"]
+
+# Repos (`path`) or single branches (`path@branch`) to leave alone.
+exclude = ["~/repos/shuuchuu/old-thing", "*@backup/*"]
+```
+
+Exclude entries take shell wildcards, `*` matching `/` too: `*@backup/*`
+leaves out every `backup/` branch of every repo, which `update` would
+otherwise bring up to date like any other.
+
+There's no list of repos to maintain: on every run copierz scans the roots
+for git repos, and every local branch of each (via `git show
+branch:.copier-answers.yml`, no checkout needed) for a Copier answers file.
+It stops descending at a repo, and skips hidden directories and linked
+worktrees.
+
+A branch can also carry Copier projects nested in subdirectories, each with
+its own answers file (say a vendored `labs/`): each is tracked on its own,
+shown as `branch:labs`, and gets an update commit of its own (`Update
+template to 0.1.8 in labs`). Stacks are still made of branches: a stacked
+branch is rebased once, whatever projects it carries. Exclude a nested
+project with its path, `~/repos/slides/labs`. The template comes from each answers file's `_src_path`; a
+relative one is resolved against the repo's own parent directory, which is
+where `copier copy` is virtually always run from.
+
+`--root PATH` (repeatable) scans other directories instead of the
+configured roots.
+
+## Usage
+
+```console
+$ copierz                    # same as `copierz status`
+$ copierz status --fetch     # git fetch every repo first
+$ copierz update --all       # update everything that's behind
+$ copierz update ghcli       # one repo (or REPO@BRANCH, a path, `.` for cwd)
+$ copierz resolve            # finish whatever stopped on conflicts
+$ copierz continue           # same, non-interactively, once fixed by hand
+$ copierz abort ghcli@main   # throw away a stopped update or rebase
+$ copierz push --all --force # push what changed, rebased branches included
+$ copierz log                # template changes since the oldest version in use
+```
+
+`copierz update` commits every update that applies cleanly (`--no-commit`
+to review them first, `--no-verify` to skip pre-commit hooks). A tracked
+`uv.lock` is relocked into the update commit, since the template may have
+changed `pyproject.toml`; if `uv lock` fails, the update is left
+uncommitted, with uv's error, for you to fix and `copierz continue`. Anything
+that stops on conflicts is left for `copierz resolve`, which walks each one
+through your `git mergetool`, then offers to review the result in your
+`git difftool` and commit it.
+
+## Pushing
+
+`copierz push` fetches, then pushes every selected branch that is ahead of
+the remote branch it tracks. Branches rebased by `update` need `--force`;
+they're then pushed with `--force-with-lease` on the fetched remote tip, and
+only if that tip is in the branch's reflog — i.e. the remote holds nothing
+the branch didn't have, so the force can't drop anyone else's work. Branches
+behind or diverged from their remote are never pushed, and `--dry-run` shows
+what would happen.
+
+## Scripting and agents
+
+`status`, `update`, `continue`, `abort`, `push` and `log` take `--json` to print a
+single JSON document on stdout (errors go to stderr, exit code 2):
+
+- `status --json`: `{"branches": [{repo, branch, subproject, template,
+  status, current, latest, parent, checkout, unmerged, detail}]}`, with
+  `subproject` `null` for the repo's root project, and `status`
+  one of `up_to_date`, `behind`, `blocked`, `in_progress`, `conflicts`,
+  `error`.
+- `update --json` / `continue --json`: `{"outcomes": [{repo, branch,
+  subproject, outcome, checkout, detail}]}`, with `outcome` one of `updated`,
+  `rebased`, `uncommitted`, `conflicts`, `skipped`, `failed`. The exit code
+  is 1 if anything stopped (conflicts, uncommitted, failed).
+- `abort --json --yes`: `{"aborted": [...]}`, same fields as `status`.
+- `push --json`: `{"branches": [{repo, branch, state, remote, commits,
+  detail}]}`, with `state` one of `up_to_date`, `ahead`, `rewritten`,
+  `behind`, `diverged`, `no_upstream`. The exit code is 1 if a branch
+  couldn't be pushed.
+- `log --json`: `{"templates": [{template, oldest, latest, commits: [{sha,
+  subject, refs}], in_use: {version: ["repo@branch", ...]}}]}`.
+
+`resolve` is interactive; the non-interactive path is to edit the files
+listed under `unmerged` in the `checkout` directory, `git add` them, and run
+`copierz continue`.
+
+## Stacked branches
+
+Branches are often stacked: `solution` on `main`, `main-en` as a
+translation commit on top of `main`, and so on, kept up to date by
+rebasing. copierz detects this from the history: a branch is stacked on
+another if it has commits of its own past their merge base, while the other
+has none except template updates (commits touching the answers file). The
+closest such branch is the parent; `copierz status` shows the stacks as a
+tree.
+
+A copy of a branch's own past tip (a backup, or a branch made from it with
+no commits yet) looks just like a parent in the history, so copierz asks the
+reflogs who got to that commit first: a copy arrives after the branch it
+copies, while a child is created, reset or rebased onto its parent after the
+parent got there. Reflogs expire (after 90 days by default), so `exclude`
+backups you keep longer.
+
+`copierz update` then only runs `copier update` on the bottom branch of each
+stack, and rebases the branches above onto their parent once it's done.
+Selecting any branch of a stack updates the whole stack. A branch that
+stops on conflicts holds back the branches stacked on it, until `copierz
+resolve` (or `continue`) finishes it and rebases them. During these rebases
+the answers file follows the parent: a conflict there only comes from a
+stale template update made on the branch itself, so it's resolved with the
+parent's version, and a commit left empty by that is dropped. A `uv.lock`
+conflict is resolved by relocking from the parent's lock, and a branch whose
+lock is still stale once rebased (its own commits changed `pyproject.toml`)
+gets a `Relock uv.lock` commit on top. Rebasing
+rewrites those branches, so pushing them afterwards needs a force: see
+`copierz push --force` below.
+
+## Worktrees
+
+copierz never switches your checkout to another branch, stashes, or
+discards your changes. A branch checked out somewhere (your main checkout or
+any worktree) is updated there, and only if it's clean. Any other branch is
+updated in a temporary worktree under `~/.cache/copierz/worktrees/`, so a
+dirty `main` doesn't hold back its siblings. That worktree is removed once
+its branch is committed, and stays (its path is shown) while it has
+conflicts to resolve.
+
+## Statuses
+
+- `up to date`: the branch's answers file records the template's latest
+  version (highest PEP 440 git tag, else `HEAD`, as Copier itself does).
+- `behind`: an update is available; for a stacked branch, it'll come from
+  rebasing onto its parent.
+- `behind, dirty`: the branch is checked out with uncommitted changes, so
+  it can't be updated until you commit or stash them.
+- `conflicts`: an update or rebase stopped on conflicts; run `copierz
+  resolve`.
+- `to commit`: an update was applied (or its conflicts resolved) but not
+  committed yet; run `copierz resolve`.
+- `error`: the template can't be found or read.
+
+Conflicts come out exactly as a `git merge` conflict would (Copier runs a
+real 3-way `git merge-file` under the hood): conflict markers in the file,
+and the file listed as unmerged by `git status`.
+
+## Releasing
+
+1. `uv run bumpver update --minor` (or `--patch`, `--major`): bumps, commits, tags
+   and pushes.
+2. `uv run doit publish`: builds and uploads to PyPI with the token of
+   `creds.env`, a gitignored file at the repository's root holding one line,
+   `export UV_PUBLISH_TOKEN=pypi-...`, readable by you only (`chmod 400`).

copierz-0.1.0/README.md

@@ -0,0 +1,166 @@
+# `copierz`
+
+A CLI to track the git repos — and every branch of them — generated from
+[Copier](https://copier.readthedocs.io/) templates, see which are behind
+their template, and bring them up to date in one go.
+
+## Configuring
+
+copierz reads `~/.config/copierz/config.toml` (or `$XDG_CONFIG_HOME`, or
+`--config PATH`):
+
+```toml
+# Scanned recursively on every run.
+roots = ["~/repos"]
+
+# Repos (`path`) or single branches (`path@branch`) to leave alone.
+exclude = ["~/repos/shuuchuu/old-thing", "*@backup/*"]
+```
+
+Exclude entries take shell wildcards, `*` matching `/` too: `*@backup/*`
+leaves out every `backup/` branch of every repo, which `update` would
+otherwise bring up to date like any other.
+
+There's no list of repos to maintain: on every run copierz scans the roots
+for git repos, and every local branch of each (via `git show
+branch:.copier-answers.yml`, no checkout needed) for a Copier answers file.
+It stops descending at a repo, and skips hidden directories and linked
+worktrees.
+
+A branch can also carry Copier projects nested in subdirectories, each with
+its own answers file (say a vendored `labs/`): each is tracked on its own,
+shown as `branch:labs`, and gets an update commit of its own (`Update
+template to 0.1.8 in labs`). Stacks are still made of branches: a stacked
+branch is rebased once, whatever projects it carries. Exclude a nested
+project with its path, `~/repos/slides/labs`. The template comes from each answers file's `_src_path`; a
+relative one is resolved against the repo's own parent directory, which is
+where `copier copy` is virtually always run from.
+
+`--root PATH` (repeatable) scans other directories instead of the
+configured roots.
+
+## Usage
+
+```console
+$ copierz                    # same as `copierz status`
+$ copierz status --fetch     # git fetch every repo first
+$ copierz update --all       # update everything that's behind
+$ copierz update ghcli       # one repo (or REPO@BRANCH, a path, `.` for cwd)
+$ copierz resolve            # finish whatever stopped on conflicts
+$ copierz continue           # same, non-interactively, once fixed by hand
+$ copierz abort ghcli@main   # throw away a stopped update or rebase
+$ copierz push --all --force # push what changed, rebased branches included
+$ copierz log                # template changes since the oldest version in use
+```
+
+`copierz update` commits every update that applies cleanly (`--no-commit`
+to review them first, `--no-verify` to skip pre-commit hooks). A tracked
+`uv.lock` is relocked into the update commit, since the template may have
+changed `pyproject.toml`; if `uv lock` fails, the update is left
+uncommitted, with uv's error, for you to fix and `copierz continue`. Anything
+that stops on conflicts is left for `copierz resolve`, which walks each one
+through your `git mergetool`, then offers to review the result in your
+`git difftool` and commit it.
+
+## Pushing
+
+`copierz push` fetches, then pushes every selected branch that is ahead of
+the remote branch it tracks. Branches rebased by `update` need `--force`;
+they're then pushed with `--force-with-lease` on the fetched remote tip, and
+only if that tip is in the branch's reflog — i.e. the remote holds nothing
+the branch didn't have, so the force can't drop anyone else's work. Branches
+behind or diverged from their remote are never pushed, and `--dry-run` shows
+what would happen.
+
+## Scripting and agents
+
+`status`, `update`, `continue`, `abort`, `push` and `log` take `--json` to print a
+single JSON document on stdout (errors go to stderr, exit code 2):
+
+- `status --json`: `{"branches": [{repo, branch, subproject, template,
+  status, current, latest, parent, checkout, unmerged, detail}]}`, with
+  `subproject` `null` for the repo's root project, and `status`
+  one of `up_to_date`, `behind`, `blocked`, `in_progress`, `conflicts`,
+  `error`.
+- `update --json` / `continue --json`: `{"outcomes": [{repo, branch,
+  subproject, outcome, checkout, detail}]}`, with `outcome` one of `updated`,
+  `rebased`, `uncommitted`, `conflicts`, `skipped`, `failed`. The exit code
+  is 1 if anything stopped (conflicts, uncommitted, failed).
+- `abort --json --yes`: `{"aborted": [...]}`, same fields as `status`.
+- `push --json`: `{"branches": [{repo, branch, state, remote, commits,
+  detail}]}`, with `state` one of `up_to_date`, `ahead`, `rewritten`,
+  `behind`, `diverged`, `no_upstream`. The exit code is 1 if a branch
+  couldn't be pushed.
+- `log --json`: `{"templates": [{template, oldest, latest, commits: [{sha,
+  subject, refs}], in_use: {version: ["repo@branch", ...]}}]}`.
+
+`resolve` is interactive; the non-interactive path is to edit the files
+listed under `unmerged` in the `checkout` directory, `git add` them, and run
+`copierz continue`.
+
+## Stacked branches
+
+Branches are often stacked: `solution` on `main`, `main-en` as a
+translation commit on top of `main`, and so on, kept up to date by
+rebasing. copierz detects this from the history: a branch is stacked on
+another if it has commits of its own past their merge base, while the other
+has none except template updates (commits touching the answers file). The
+closest such branch is the parent; `copierz status` shows the stacks as a
+tree.
+
+A copy of a branch's own past tip (a backup, or a branch made from it with
+no commits yet) looks just like a parent in the history, so copierz asks the
+reflogs who got to that commit first: a copy arrives after the branch it
+copies, while a child is created, reset or rebased onto its parent after the
+parent got there. Reflogs expire (after 90 days by default), so `exclude`
+backups you keep longer.
+
+`copierz update` then only runs `copier update` on the bottom branch of each
+stack, and rebases the branches above onto their parent once it's done.
+Selecting any branch of a stack updates the whole stack. A branch that
+stops on conflicts holds back the branches stacked on it, until `copierz
+resolve` (or `continue`) finishes it and rebases them. During these rebases
+the answers file follows the parent: a conflict there only comes from a
+stale template update made on the branch itself, so it's resolved with the
+parent's version, and a commit left empty by that is dropped. A `uv.lock`
+conflict is resolved by relocking from the parent's lock, and a branch whose
+lock is still stale once rebased (its own commits changed `pyproject.toml`)
+gets a `Relock uv.lock` commit on top. Rebasing
+rewrites those branches, so pushing them afterwards needs a force: see
+`copierz push --force` below.
+
+## Worktrees
+
+copierz never switches your checkout to another branch, stashes, or
+discards your changes. A branch checked out somewhere (your main checkout or
+any worktree) is updated there, and only if it's clean. Any other branch is
+updated in a temporary worktree under `~/.cache/copierz/worktrees/`, so a
+dirty `main` doesn't hold back its siblings. That worktree is removed once
+its branch is committed, and stays (its path is shown) while it has
+conflicts to resolve.
+
+## Statuses
+
+- `up to date`: the branch's answers file records the template's latest
+  version (highest PEP 440 git tag, else `HEAD`, as Copier itself does).
+- `behind`: an update is available; for a stacked branch, it'll come from
+  rebasing onto its parent.
+- `behind, dirty`: the branch is checked out with uncommitted changes, so
+  it can't be updated until you commit or stash them.
+- `conflicts`: an update or rebase stopped on conflicts; run `copierz
+  resolve`.
+- `to commit`: an update was applied (or its conflicts resolved) but not
+  committed yet; run `copierz resolve`.
+- `error`: the template can't be found or read.
+
+Conflicts come out exactly as a `git merge` conflict would (Copier runs a
+real 3-way `git merge-file` under the hood): conflict markers in the file,
+and the file listed as unmerged by `git status`.
+
+## Releasing
+
+1. `uv run bumpver update --minor` (or `--patch`, `--major`): bumps, commits, tags
+   and pushes.
+2. `uv run doit publish`: builds and uploads to PyPI with the token of
+   `creds.env`, a gitignored file at the repository's root holding one line,
+   `export UV_PUBLISH_TOKEN=pypi-...`, readable by you only (`chmod 400`).

copierz-0.1.0/pyproject.toml

@@ -0,0 +1,92 @@
+[project]
+dependencies = [
+    "copier >= 9.9, < 10",
+    "packaging >= 24",
+    "pyyaml >= 6, < 7",
+    "rich >= 13",
+]
+description = "CLI to track and apply Copier updates across a fleet of git repositories."
+homepage = "https://github.com/shuuchuu/copierz"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+name = "copierz"
+readme = "README.md"
+requires-python = ">= 3.13"
+version = "0.1.0"
+
+[[project.authors]]
+name = "m09"
+email = "142691+m09@users.noreply.github.com"
+
+[project.scripts]
+copierz = "copierz.cli:main"
+
+[dependency-groups]
+dev = [
+    "bumpver >= 2026.1132",
+    "doit >= 0.37",
+    "prek >= 0.5.7",
+    "pyrefly >= 1.4",
+    "pytest >= 9",
+    "ruff >= 0.17",
+]
+
+[tool.ruff]
+target-version = "py313"
+
+[tool.ruff.lint]
+ignore = [
+    "D1",
+    "incorrect-blank-line-before-class",
+    "multi-line-summary-second-line",
+    "non-empty-init-module",
+]
+preview = true
+select = [
+    "A",
+    "B",
+    "C",
+    "D",
+    "DOC",
+    "E",
+    "EM",
+    "F",
+    "I",
+    "N",
+    "PIE",
+    "PTH",
+    "RET",
+    "RUF",
+    "SIM",
+    "SLF",
+    "TC",
+    "UP",
+    "W",
+]
+
+[tool.ruff.lint.pydocstyle]
+convention = "google"
+
+[tool.pyrefly]
+search-path = ["."]
+
+[bumpver]
+commit = true
+tag = true
+push = true
+commit_message = "Bump version to {new_version}"
+current_version = "0.1.0"
+pre_commit_hook = "scripts/bumpver_pre_commit.sh"
+tag_message = "{new_version}"
+version_pattern = "MAJOR.MINOR.PATCH"
+
+[bumpver.file_patterns]
+"pyproject.toml" = [
+    '^version = "{version}"$',
+    '^current_version = "{version}"$',
+]
+"src/copierz/__init__.py" = ['^__version__ = "{version}"$']
+
+[build-system]
+build-backend = "uv_build"
+requires = ["uv_build>=0.13.6,<0.14.0"]