Skip to content

docs: warn that a relative local template path breaks copier update #374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eduralph merged 1 commit into from
Jul 31, 2026
+10 −0
Merged

docs: warn that a relative local template path breaks copier update #374

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/01-render-and-integrate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,16 @@ copier copy gh:eduralph/pdca-harness ../gramps-testbed-v2
cd ../gramps-testbed-v2
```

> **Rendering from a local checkout instead?** Give copier a `gh:`/`https:`
> URL (as above) or an **absolute** path. Copier records the source argument
> verbatim as `_src_path` in `.copier-answers.yml`, and `copier update`
> resolves it from the *project* directory — a path relative to your render
> cwd never resolves there, so the first `copier update` fails
> ([copier#335](https://github.com/copier-org/copier/issues/335); fix pending
> in [copier#2717](https://github.com/copier-org/copier/pull/2717)). Already
> rendered that way? Hand-edit `_src_path` to the template URL or an absolute
> path — that's the whole repair.

The prompts (from [`copier.yml`](../copier.yml)) and what gramps answered:

| Prompt | What it sets | gramps-testbed-v2 |
Expand Down
Loading