fix(docs): avoid <> as it breaks crowdin

This commit is contained in:
Andrey Nering
2023-06-10 21:06:20 -03:00
parent 9ee714d048
commit a452f0b4bd

View File

@@ -21,10 +21,10 @@ are intended to replace.
You can enable an experimental feature by: You can enable an experimental feature by:
1. Using the `--x-<feature>` flag. This is intended for one-off invocations of 1. Using the `--x-{feature}` flag. This is intended for one-off invocations of
Task to test out experimental features. You can also disable a feature by Task to test out experimental features. You can also disable a feature by
specifying a falsy value such as `--x-<feature>=false`. specifying a falsy value such as `--x-{feature}=false`.
1. Using the `TASK_X_<FEATURE>=1` environment variable. This is intended for 1. Using the `TASK_X_{FEATURE}=1` environment variable. This is intended for
permanently enabling experimental features in your environment. permanently enabling experimental features in your environment.
Flags will always override environment variables. Flags will always override environment variables.
@@ -38,15 +38,15 @@ existing Taskfiles to the new behavior.
<!-- EXPERIMENT TEMPLATE - Include sections as necessary... <!-- EXPERIMENT TEMPLATE - Include sections as necessary...
### ![experiment] <Feature> ([#<issue>](https://github.com/go-task/task/issues/<issue>)), ...) ### ![experiment] <Feature> ([#{issue}](https://github.com/go-task/task/issues/{issue})), ...)
- Flag to enable: `--x-<feature>` - Flag to enable: `--x-{feature}`
- Env to enable: `TASK_X_<feature>` - Env to enable: `TASK_X_{feature}`
- Deprecates: <list any existing functionality that will be deprecated by this experiment> - Deprecates: {list any existing functionality that will be deprecated by this experiment}
<Short description of the feature> {Short description of the feature}
<Short explanation of how users should migrate to the new behavior> {Short explanation of how users should migrate to the new behavior}
--> -->