You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
12
12
13
13
### Changed
14
14
-**Breaking:**`-r/--root` is now a global `git workspace` option instead of a per-command flag for workspace-aware commands. Use `git workspace -r /path/to/workspace up`, `git workspace -r /path/to/workspace compose`, etc. instead of placing `-r` after the subcommand. `init`, `clone`, and `cache` do not use this flag.
15
-
-**Breaking:** Copy assets are now rendered as Jinja2 templates only when their source filename ends in `.j2`. Files without `.j2` are copied verbatim, so assets that incidentally contain `{{ … }}` or `{% … %}` (shell scripts, dockerfiles using Bash `${VAR}`, etc.) are no longer silently rewritten. The target path is taken verbatim from the manifest — the `.j2` suffix is **not** stripped automatically; if you want the rendered file to be `docker-compose.override.yml`, write `source = "docker-compose.override.yml.j2"` and `target = "docker-compose.override.yml"`. Migrate by renaming any asset that relies on Jinja substitution from `<name>` to `<name>.j2` and updating the matching `[[copy]]``source` field.
15
+
-**Breaking:** Copy assets are now rendered as Jinja2 templates only when their source filename ends in `.j2`. Files without `.j2` are copied verbatim, so assets that incidentally contain `{{ … }}` or `{% … %}` (shell scripts, dockerfiles using Bash `${VAR}`, etc.) are no longer silently rewritten. For top-level copies the target path is taken verbatim from the manifest — the `.j2` suffix is **not** stripped automatically; if you want the rendered file to be `docker-compose.override.yml`, write `source = "docker-compose.override.yml.j2"` and `target = "docker-compose.override.yml"`. Inside a directory copy, the `.j2` suffix **is** stripped from each rendered file's on-disk name (e.g. `vscode/settings.json.j2` becomes `.vscode/settings.json`), since the manifest does not name nested files individually. Migrate by renaming any asset that relies on Jinja substitution from `<name>` to `<name>.j2` and updating the matching `[[copy]]``source` field.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -384,7 +384,7 @@ overwrite = false
384
384
<summary><i>Templating</i></summary>
385
385
<br/>
386
386
387
-
Files in `.workspace/assets/` whose name ends in `.j2` are rendered as [Jinja2](https://jinja.palletsprojects.com/) templates. Files without `.j2` are copied verbatim. The target path is whatever you write in the manifest — the `.j2` suffix is **not** stripped automatically, so use an explicit `target` if you want a different output name:
387
+
Files in `.workspace/assets/` whose name ends in `.j2` are rendered as [Jinja2](https://jinja.palletsprojects.com/) templates. Files without `.j2` are copied verbatim. For top-level copies the target path is whatever you write in the manifest — the `.j2` suffix is **not** stripped automatically, so use an explicit `target` if you want a different output name:
388
388
389
389
```toml
390
390
[[copy]]
@@ -419,7 +419,7 @@ log_level: debug
419
419
{% endif %}
420
420
```
421
421
422
-
Unknown variables are left verbatim (e.g. `{{ GIT_WORKSPACE_TYPO }}` is written as-is so typos are obvious). Only `GIT_WORKSPACE_*` keys are exposed — the host process environment is not. Plain (non-`.j2`) files — text or binary — are copied byte-for-byte. In a directory copy, each file is rendered or copied based on its own suffix; on-disk filenames are preserved in the output. `git workspace doctor` flags unknown variables and template syntax errors in `.j2` files.
422
+
Unknown variables are left verbatim (e.g. `{{ GIT_WORKSPACE_TYPO }}` is written as-is so typos are obvious). Only `GIT_WORKSPACE_*` keys are exposed — the host process environment is not. Plain (non-`.j2`) files — text or binary — are copied byte-for-byte. In a directory copy, each file is rendered or copied based on its own suffix, and the trailing `.j2` is stripped from rendered files (e.g. `vscode/settings.json.j2` becomes `.vscode/settings.json`); plain files keep their on-disk name. `git workspace doctor` flags unknown variables and template syntax errors in `.j2` files.
0 commit comments