Skip to content

Commit b30aacb

Browse files
author
Murat
committed
docs(website): fix build
1 parent ebc052f commit b30aacb

File tree

3 files changed

+4829
-2497
lines changed

3 files changed

+4829
-2497
lines changed

website/docs/upgrade/configuration.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ title: Configuration
66

77
The configuration file is where you define the overall structure of your upgrade process.
88

9-
| Property | Type | Description |
10-
|:------------|:-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
11-
| env | object | Allows you to define variables that can be used throughout the configuration. These variables can hold values that you want to reuse in different parts of your tasks. Variables defined in `env` can be referenced using the `$[var_name]` convention. |
12-
| pre_install | {imports, steps} | This optional stage can be used to import or run steps before module installation. |
13-
| imports | array of strings | Relative paths of files and folders which will be imported during upgrade. |
14-
| steps | array of objects | This is where you define individual integration tasks and their properties. Each task should have a `task` field that specifies the type of task to perform. |
9+
| Property | Type | Description |
10+
|:------------|:-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
11+
| env | object | Allows you to define variables that can be used throughout the configuration. These variables can hold values that you want to reuse in different parts of your tasks. Variables defined in `env` can be referenced using the `$[var_name]` convention. |
12+
| pre_install | `{imports, steps}` | This optional stage can be used to import or run steps before module installation. |
13+
| imports | array of strings | Relative paths of files and folders which will be imported during upgrade. |
14+
| steps | array of objects | This is where you define individual integration tasks and their properties. Each task should have a `task` field that specifies the type of task to perform. |
1515

1616
#### Example:
1717

0 commit comments

Comments
 (0)