mirror of
https://github.com/go-task/task.git
synced 2025-05-19 22:33:35 +02:00
docs: broken links
This commit is contained in:
parent
b5d573fbd9
commit
f5121de468
@ -83,10 +83,10 @@ add a new section. If you're updating an existing feature, ensure that the
|
|||||||
documentation and any examples are up-to-date. Ensure that any examples follow
|
documentation and any examples are up-to-date. Ensure that any examples follow
|
||||||
the [Taskfile Styleguide](/styleguide).
|
the [Taskfile Styleguide](/styleguide).
|
||||||
|
|
||||||
If you added a new field, command or flag, ensure that you add it to the
|
If you added a new command or flag, ensure that you add it to the [CLI
|
||||||
[API Reference](/api). New fields also need to be added to the [JSON
|
Reference](/reference/cli). New fields also need to be added to the [Schema
|
||||||
Schema][json-schema]. The descriptions for fields in the API reference and the
|
Reference](/reference/schema) and [JSON Schema][json-schema]. The descriptions
|
||||||
schema should match.
|
for fields in the docs and the schema should match.
|
||||||
|
|
||||||
### Writing tests
|
### Writing tests
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ four groups with the following ranges:
|
|||||||
- Success (0)
|
- Success (0)
|
||||||
- General errors (1-99)
|
- General errors (1-99)
|
||||||
- Taskfile errors (100-199)
|
- Taskfile errors (100-199)
|
||||||
- Task errors (200-299)
|
- Task errors (200-255)
|
||||||
|
|
||||||
A full list of the exit codes and their descriptions can be found below:
|
A full list of the exit codes and their descriptions can be found below:
|
||||||
|
|
||||||
|
@ -938,8 +938,8 @@ information.
|
|||||||
You can use `--force` or `-f` if you want to force a task to run even when
|
You can use `--force` or `-f` if you want to force a task to run even when
|
||||||
up-to-date.
|
up-to-date.
|
||||||
|
|
||||||
Also, `task --status [tasks]...` will exit with a non-zero exit code if any of
|
Also, `task --status [tasks]...` will exit with a non-zero [exit
|
||||||
the tasks are not up-to-date.
|
code](/reference/cli#exit-codes) if any of the tasks are not up-to-date.
|
||||||
|
|
||||||
`status` can be combined with the
|
`status` can be combined with the
|
||||||
[fingerprinting](#by-fingerprinting-locally-generated-files-and-their-sources)
|
[fingerprinting](#by-fingerprinting-locally-generated-files-and-their-sources)
|
||||||
@ -1759,8 +1759,8 @@ commands are executed in the reverse order if you schedule multiple of them.
|
|||||||
:::
|
:::
|
||||||
|
|
||||||
A special variable `.EXIT_CODE` is exposed when a command exited with a non-zero
|
A special variable `.EXIT_CODE` is exposed when a command exited with a non-zero
|
||||||
exit code. You can check its presence to know if the task completed successfully
|
[exit code](/reference/cli#exit-codes). You can check its presence to know if
|
||||||
or not:
|
the task completed successfully or not:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
version: '3'
|
version: '3'
|
||||||
@ -1959,8 +1959,8 @@ tasks:
|
|||||||
```
|
```
|
||||||
|
|
||||||
Warning prompts are called before executing a task. If a prompt is denied Task
|
Warning prompts are called before executing a task. If a prompt is denied Task
|
||||||
will exit with [exit code](/api#exit-codes) 205. If approved, Task will continue
|
will exit with [exit code](/reference/cli#exit-codes) 205. If approved, Task
|
||||||
as normal.
|
will continue as normal.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
❯ task example
|
❯ task example
|
||||||
|
@ -83,10 +83,10 @@ add a new section. If you're updating an existing feature, ensure that the
|
|||||||
documentation and any examples are up-to-date. Ensure that any examples follow
|
documentation and any examples are up-to-date. Ensure that any examples follow
|
||||||
the [Taskfile Styleguide](/styleguide).
|
the [Taskfile Styleguide](/styleguide).
|
||||||
|
|
||||||
If you added a new field, command or flag, ensure that you add it to the
|
If you added a new command or flag, ensure that you add it to the [CLI
|
||||||
[API Reference](/api). New fields also need to be added to the [JSON
|
Reference](/reference/cli). New fields also need to be added to the [Schema
|
||||||
Schema][json-schema]. The descriptions for fields in the API reference and the
|
Reference](/reference/schema) and [JSON Schema][json-schema]. The descriptions
|
||||||
schema should match.
|
for fields in the docs and the schema should match.
|
||||||
|
|
||||||
### Writing tests
|
### Writing tests
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ four groups with the following ranges:
|
|||||||
- Success (0)
|
- Success (0)
|
||||||
- General errors (1-99)
|
- General errors (1-99)
|
||||||
- Taskfile errors (100-199)
|
- Taskfile errors (100-199)
|
||||||
- Task errors (200-299)
|
- Task errors (200-255)
|
||||||
|
|
||||||
A full list of the exit codes and their descriptions can be found below:
|
A full list of the exit codes and their descriptions can be found below:
|
||||||
|
|
||||||
|
@ -938,8 +938,8 @@ information.
|
|||||||
You can use `--force` or `-f` if you want to force a task to run even when
|
You can use `--force` or `-f` if you want to force a task to run even when
|
||||||
up-to-date.
|
up-to-date.
|
||||||
|
|
||||||
Also, `task --status [tasks]...` will exit with a non-zero exit code if any of
|
Also, `task --status [tasks]...` will exit with a non-zero [exit
|
||||||
the tasks are not up-to-date.
|
code](/reference/cli#exit-codes) if any of the tasks are not up-to-date.
|
||||||
|
|
||||||
`status` can be combined with the
|
`status` can be combined with the
|
||||||
[fingerprinting](#by-fingerprinting-locally-generated-files-and-their-sources)
|
[fingerprinting](#by-fingerprinting-locally-generated-files-and-their-sources)
|
||||||
@ -1759,8 +1759,8 @@ commands are executed in the reverse order if you schedule multiple of them.
|
|||||||
:::
|
:::
|
||||||
|
|
||||||
A special variable `.EXIT_CODE` is exposed when a command exited with a non-zero
|
A special variable `.EXIT_CODE` is exposed when a command exited with a non-zero
|
||||||
exit code. You can check its presence to know if the task completed successfully
|
[exit code](/reference/cli#exit-codes). You can check its presence to know if
|
||||||
or not:
|
the task completed successfully or not:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
version: '3'
|
version: '3'
|
||||||
@ -1959,8 +1959,8 @@ tasks:
|
|||||||
```
|
```
|
||||||
|
|
||||||
Warning prompts are called before executing a task. If a prompt is denied Task
|
Warning prompts are called before executing a task. If a prompt is denied Task
|
||||||
will exit with [exit code](/api#exit-codes) 205. If approved, Task will continue
|
will exit with [exit code](/reference/cli#exit-codes) 205. If approved, Task
|
||||||
as normal.
|
will continue as normal.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
❯ task example
|
❯ task example
|
||||||
|
Loading…
x
Reference in New Issue
Block a user