v3.44.1

* chore: replace PPRemoveAbsolutePaths with generic fixture template data

* chore: update to goldie v2.7.1

.editorconfig

@@ -8,6 +8,6 @@ charset = utf-8
 trim_trailing_whitespace = true
 indent_style = tab
 
-[*.{md,yml,yaml,json,toml,htm,html,js,css,svg,sh,bash,fish}]
+[*.{md,mdx,yml,yaml,json,toml,htm,html,js,ts,css,svg,sh,bash,fish}]
 indent_style = space
 indent_size = 2

.gitattributes

@@ -1 +1,2 @@
 * text=auto
+*.mdx -linguist-detectable

.github/CODE_OF_CONDUCT.md

@@ -1,46 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at andrey@nering.com.br. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -1,14 +0,0 @@
-## You can find our [contribution guide on our website][contributing]
-
-- Please read it carefully before opening a PR.
-- If you have any questions, you can:
-  - [Open an issue][issues]
-  - [Create a discussion][discussions]
-  - [Chat to us on Discord][discord]
-
-<!-- prettier-ignore-start -->
-[contributing]: https://taskfile.dev/contributing
-[issues]: https://github.com/go-task/task/issues
-[discussions]: https://github.com/go-task/task/discussions
-[discord]: https://discord.gg/6TY36E39UK
-<!-- prettier-ignore-end -->

.github/FUNDING.yml

@@ -1,3 +0,0 @@
-github: [andreynering, pd93]
-open_collective: task
-custom: https://taskfile.dev/donate/

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,20 +0,0 @@
----
-name: Bug Report
-about: Use this to report bugs and issues
----
-
-<!--
-
-Thanks for your bug report!
-
-Before submitting this issue, please make sure the same problem was not
-already reported by someone else.
-
-Please describe the bug you're facing. Consider pasting example Taskfiles
-showing how to reproduce the problem.
-
--->
-
-- Task version:
-- Operating system:
-- Experiments enabled:

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,69 @@
+name: '🐞 Bug Report'
+description: Report a bug in Task.
+labels: ['state: needs-triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your bug report!
+
+        Before submitting, please check the list of [existing issues](https://github.com/go-task/task/issues) and make sure the same bug was not already reported by someone else.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the bug you're seeing.
+      placeholder: |
+        - What did you do?
+        - What did you expect to happen?
+        - What happened instead?
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: What version(s) of Task is the issue occurring on?
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      description: What operating system(s) is the issue occurring on?
+    validations:
+      required: true
+
+  - type: dropdown
+    id: experiments
+    attributes:
+      label: Experiments Enabled
+      description: Do you have any experiments enabled? You can check by running `task --experiments`.
+      multiple: true
+      options:
+        - Env Precedence
+        - Gentle Force
+        - Map Variables (1)
+        - Map Variables (2)
+        - Remote Taskfiles
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Example Taskfile
+      description: |
+        If you have a Taskfile that reproduces the issue, please paste it here.
+        This will be automatically formatted into code, so no need for backticks.
+      render: YAML
+      placeholder: |
+        version: '3'
+
+        tasks:
+          default:
+            cmds:
+              - 'echo "This Taskfile is buggy :("'

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Extension for Visual Studio Code
+  - name: '🔌 Task for Visual Studio Code'
     url: https://github.com/go-task/vscode-task
-    about: Issues related to the Visual Studio Code extension should be opened here.
-  - name: Help forum on Discord
-    url: https://discord.gg/6TY36E39UK
-    about: 'The Discord #help channel is the best way to get help from the community.'
-  - name: Questions, Ideas and General Discussions
+    about: 'Issues related to the Visual Studio Code extension should be opened here.'
+  - name: '💬 Help forum on Discord'
+    url: https://discord.com/channels/974121106208354339/1025054680289660989
+    about: 'The #help channel on our Discord is the best way to get help from the community.'
+  - name: '❓ Questions, Ideas and General Discussions'
     url: https://github.com/go-task/task/discussions
-    about: Ask questions and discuss general ideas with the community.
+    about: 'Ask questions and discuss general ideas with the community.'

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,15 +0,0 @@
----
-name: Feature Request
-about: Use this to make feature requests
----
-
-<!--
-
-Describe in detail what feature do you want to see in Task.
-Give examples if possible.
-
-Please, search if this wasn't proposed before, and if this is more like an idea
-than a strong feature request, consider opening a
-[discussion](https://github.com/go-task/task/discussions) instead.
-
--->

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,23 @@
+name: '✨ Feature Request'
+description: Suggest a new feature or enhancement for Task.
+labels: ['state: needs-triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your feature request!
+
+        Before submitting, please check the list of [existing issues](https://github.com/go-task/task/issues) and make sure the same change was not already requested by someone else.
+        If your request is more of an idea than a feature request, consider opening a [discussion](https://github.com/go-task/task/discussions) instead.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the feature/enhancement you want to see in Task.
+      placeholder: |
+        - Give a general overview of the feature/enhancement.
+        - Explain problem is the change trying to solve.
+        - Give examples of how you would use the feature.
+    validations:
+      required: true

.github/dependabot.yml

@@ -1,24 +0,0 @@
-version: 2
-
-updates:
-  - package-ecosystem: gomod
-    directory: /
-    schedule:
-      interval: weekly
-      day: saturday
-      time: '08:00'
-      timezone: America/Sao_Paulo
-    labels:
-      - "area: dependencies"
-      - "lang: go"
-
-  - package-ecosystem: npm
-    directory: /
-    schedule:
-      interval: weekly
-      day: saturday
-      time: '08:00'
-      timezone: America/Sao_Paulo
-    labels:
-      - "area: dependencies"
-      - "lang: javascript"

.github/pull_request_template.md

@@ -1,5 +1,9 @@
-> Thanks for your pull request, we really appreciate contributions!
->
-> Please understand that it may take some time to be reviewed.
->
-> Also, make sure to follow the [Contribution Guide](https://taskfile.dev/contributing/).
+<!--
+
+Thanks for your pull request, we really appreciate contributions!
+
+Please understand that it may take some time to be reviewed.
+
+Also, make sure to follow the [Contribution Guide](https://taskfile.dev/contributing/).
+
+-->

.github/renovate.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:recommended",
+    "group:allNonMajor",
+    "schedule:weekly",
+    ":semanticCommitTypeAll(chore)"
+  ],
+  "mode": "full",
+  "addLabels":["area: dependencies"],
+  "packageRules": [
+    {
+      "matchManagers": ["github-actions"],
+      "addLabels": ["area: github actions"]
+    },
+    {
+      "matchCategories": ["js", "node"],
+      "addLabels": ["lang: javascript"]
+    },
+    {
+      "matchCategories": ["golang"],
+      "addLabels": ["lang: go"]
+    }
+  ]
+}

.github/workflows/issue-awaiting-response.yml

@@ -8,7 +8,7 @@ jobs:
   issue-awaiting-response:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |

.github/workflows/issue-closed.yml

@@ -8,7 +8,7 @@ jobs:
   issue-closed:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |

.github/workflows/issue-experiment.yml

@@ -6,10 +6,10 @@ on:
 
 jobs:
   issue-experiment-proposed:
-    if: github.event.label.name == format('experiment{0} proposed', ':')
+    if: github.event.label.name == format('status{0} proposed', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -20,10 +20,10 @@ jobs:
               body: 'This issue has been marked as an experiment proposal! :test_tube: It will now enter a period of consultation during which we encourage the community to provide feedback on the proposed design. Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-draft:
-    if: github.event.label.name == format('experiment{0} draft', ':')
+    if: github.event.label.name == format('status{0} draft', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -34,10 +34,10 @@ jobs:
               body: 'This experiment has been marked as a draft! :sparkles: This means that an initial implementation has been added to the latest release of Task! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-candidate:
-    if: github.event.label.name == format('experiment{0} candidate', ':')
+    if: github.event.label.name == format('status{0} candidate', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -48,10 +48,10 @@ jobs:
               body: 'This experiment has been marked as a candidate! :fire: This means that the  implementation is nearing completion and we are entering a period for final comments and feedback! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-stable:
-    if: github.event.label.name == format('experiment{0} stable', ':')
+    if: github.event.label.name == format('status{0} stable', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -62,10 +62,10 @@ jobs:
               body: 'This experiment has been marked as stable! :metal: This means that the  implementation is now final and ready to be released. No more changes will be made and the experiment is safe to use in production! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-released:
-    if: github.event.label.name == format('experiment{0} released', ':')
+    if: github.event.label.name == format('status{0} released', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -82,10 +82,10 @@ jobs:
               state: 'closed'
             })
   issue-experiment-abandoned:
-    if: github.event.label.name == format('experiment{0} abandoned', ':')
+    if: github.event.label.name == format('status{0} abandoned', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |
@@ -102,10 +102,10 @@ jobs:
               state: 'closed'
             })
   issue-experiment-superseded:
-    if: github.event.label.name == format('experiment{0} superseded', ':')
+    if: github.event.label.name == format('status{0} superseded', ':')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |

.github/workflows/issue-needs-triage.yml

@@ -8,7 +8,7 @@ jobs:
   issue-needs-triage:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v7
         with:
           github-token: ${{secrets.GH_PAT}}
           script: |

.github/workflows/lint.yml

@@ -13,19 +13,19 @@ jobs:
     name: Lint
     strategy:
       matrix:
-        go-version: [1.21.x, 1.22.x]
+        go-version: [1.23.x, 1.24.x]
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/setup-go@v3
+      - uses: actions/setup-go@v5
         with:
           go-version: ${{matrix.go-version}}
 
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
       - name: golangci-lint
-        uses: golangci/golangci-lint-action@v3
+        uses: golangci/golangci-lint-action@v8
         with:
-          version: v1.55.2
+          version: v2.1.0
 
   lint-jsonschema:
     runs-on: ubuntu-latest
@@ -34,10 +34,41 @@ jobs:
         with:
           python-version: 3.12
 
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
       - name: install check-jsonschema
         run: python -m pip install 'check-jsonschema==0.27.3'
 
       - name: check-jsonschema (metaschema)
-        run: check-jsonschema --check-metaschema docs/static/schema.json
+        run: check-jsonschema --check-metaschema website/static/schema.json
+  check_doc:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Get changed files in the docs folder
+        id: changed-files-specific
+        uses: tj-actions/changed-files@v46
+        with:
+          files: website/versioned_docs/**
+
+      - uses: actions/github-script@v7
+        if: steps.changed-files-specific.outputs.any_changed == 'true'
+        with:
+          script: |
+            core.setFailed('website/versioned_docs has changed. Instead you need to update the docs in the website/docs folder.')
+  check_schema:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Get changed files in the docs folder
+        id: changed-files-specific
+        uses: tj-actions/changed-files@v46
+        with:
+          files: |
+            website/static/schema.json
+            website/static/schema-taskrc.json
+      - uses: actions/github-script@v7
+        if: steps.changed-files-specific.outputs.any_changed == 'true'
+        with:
+          script: |
+            core.setFailed('schema.json or schema-taskrc.json has changed. Instead you need to update next-schema.json or next-schema-taskrc.json.')

.github/workflows/release.yml

@@ -10,17 +10,21 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - name: Set up Go
-        uses: actions/setup-go@v3
+        uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version: 1.24.x
 
       - name: Run GoReleaser
-        uses: goreleaser/goreleaser-action@v2
+        uses: goreleaser/goreleaser-action@v6
         with:
+          distribution: goreleaser-pro
           version: latest
           args: release --clean
         env:
           GITHUB_TOKEN: ${{secrets.GH_PAT}}
+          GORELEASER_KEY: ${{secrets.GORELEASER_KEY}}

.github/workflows/sync-translated-documents.yml

@@ -1,36 +0,0 @@
-name: Sync Translations
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: "0 0 * * *"
-
-jobs:
-  sync-translated-documents:
-    runs-on: ubuntu-latest
-    if: github.repository == 'go-task/task'
-    steps:
-      - uses: actions/checkout@v3
-
-      - name: Install Task
-        uses: arduino/setup-task@v1
-        with:
-          version: 3.x
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Sync Translations
-        run: task crowdin:pull
-        env:
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-        working-directory: ./docs
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v4
-        with:
-          commit-message: "chore: sync translations"
-          title: "chore: sync translations"
-          branch: chore/sync-translations
-          delete-branch: true
-          author: task-bot <106601941+task-bot@users.noreply.github.com>
-          labels: "area: translation"
-          token: ${{ secrets.GH_PAT }}

.github/workflows/test.yml

@@ -13,18 +13,18 @@ jobs:
     name: Test
     strategy:
       matrix:
-        go-version: [1.21.x, 1.22.x]
+        go-version: [1.23.x, 1.24.x]
         platform: [ubuntu-latest, macos-latest, windows-latest]
     runs-on: ${{matrix.platform}}
     steps:
       - name: Set up Go ${{matrix.go-version}}
-        uses: actions/setup-go@v3
+        uses: actions/setup-go@v5
         with:
           go-version: ${{matrix.go-version}}
         id: go
 
       - name: Check out code into the Go module directory
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Download Go modules
         run: go mod download

.github/workflows/upload-source-documents.yml

@@ -1,38 +0,0 @@
-name: Upload Source Documents
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-jobs:
-  push_files_to_crowdin:
-    name: Push files to Crowdin
-    if: github.repository == 'go-task/task'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Verify changed files
-        id: changed-files
-        uses: tj-actions/changed-files@v41
-        with:
-          files: |
-            docs/docs
-            docs/blog
-            docs/i18n/en
-            docs/src/pages
-
-      - name: Install Task
-        uses: arduino/setup-task@v1
-        with:
-          version: 3.x
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Upload source documents
-        if: steps.changed-files.outputs.any_changed == 'true'
-        run: task crowdin:push
-        env:
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-        working-directory: ./docs

.gitignore

@@ -10,6 +10,9 @@
 # Output of the go coverage tool, specifically when used with LiteIDE
 *.out
 
+# Graphvis files
+*.gv
+
 # Project-local glide cache, RE: https://github.com/Masterminds/glide/issues/736
 .glide/
 
@@ -21,8 +24,7 @@ dist/
 
 # editors
 .idea/
-.vscode/*
-!.vscode/*-sample.json
+.vscode/settings.json
 .fleet/
 
 # exuberant ctags

.golangci.yml

@@ -1,18 +1,64 @@
-# NOTE(@andreynering): The linters listed here are additions on top of
-# those enabled by default:
-#
-# https://golangci-lint.run/usage/linters/#enabled-by-default
+version: "2"
+
+formatters:
+  enable:
+    - gofmt
+    - gofumpt
+    - goimports
+    - gci
+  settings:
+    gofmt:
+      simplify: true
+      rewrite-rules:
+        - pattern: interface{}
+          replacement: any
+    gofumpt:
+      module-path: github.com/go-task/task/v3
+    goimports:
+      local-prefixes:
+        - github.com/go-task
+    gci:
+      sections:
+        - standard
+        - default
+        - prefix(github.com/go-task)
+        - localmodule
+  exclusions:
+    generated: lax
+    paths:
+      - third_party$
+      - builtin$
+      - examples$
 
 linters:
   enable:
-    - goimports
-    - gofmt
-    - gofumpt
-
-linters-settings:
-  goimports:
-    local-prefixes: github.com/go-task/task
-  gofmt:
-    rewrite-rules:
-      - pattern: 'interface{}'
-        replacement: 'any'
+    - depguard
+    - mirror
+    - misspell
+    - noctx
+    - paralleltest
+    - thelper
+    - tparallel
+    - usetesting
+  settings:
+    depguard:
+      rules:
+        main:
+          files:
+            - $all
+            - '!$test'
+            - '!**/errors/*.go'
+          deny:
+            - pkg: errors
+              desc: Use github.com/go-task/task/v3/errors instead
+  exclusions:
+    generated: lax
+    presets:
+      - comments
+      - common-false-positives
+      - legacy
+      - std-error-handling
+    paths:
+      - third_party$
+      - builtin$
+      - examples$

.goreleaser.yml

@@ -1,3 +1,6 @@
+# yaml-language-server: $schema=https://goreleaser.com/static/schema.json
+version: 2
+
 builds:
   - binary: task
     main: ./cmd/task
@@ -11,11 +14,16 @@ builds:
       - amd64
       - arm
       - arm64
+      - riscv64
     goarm:
       - '6'
     ignore:
       - goos: darwin
         goarch: '386'
+      - goos: darwin
+        goarch: riscv64
+      - goos: windows
+        goarch: riscv64
     env:
       - CGO_ENABLED=0
     mod_timestamp: '{{ .CommitTimestamp }}'
@@ -35,13 +43,13 @@ archives:
       - completion/**/*
     format_overrides:
       - goos: windows
-        format: zip
+        formats: [zip]
 
 release:
   draft: true
 
 snapshot:
-  name_template: "{{.Tag}}"
+  version_template: "{{.Version}}"
 
 checksum:
   name_template: "task_checksums.txt"
@@ -49,8 +57,9 @@ checksum:
 nfpms:
   - vendor: Task
     homepage: https://taskfile.dev
-    maintainer: Andrey Nering <andrey@nering.com.br>
+    maintainer: The Task authors <task@taskfile.dev>
     description: Simple task runner written in Go
+    section: golang
     license: MIT
     conflicts:
       - taskwarrior
@@ -71,7 +80,7 @@ brews:
     description: Task runner / simpler Make alternative written in Go
     license: MIT
     homepage: https://taskfile.dev
-    folder: Formula
+    directory: Formula
     repository:
       owner: go-task
       name: homebrew-tap

.mockery.yaml

@@ -1,4 +1,8 @@
-with-expecter: true
-keeptree: true
-case: underscore
-output: ./internal/mocks
+all: False
+template: testify
+filename: '{{base (trimSuffix ".go" .InterfaceFile)}}_mock.go'
+packages:
+  github.com/go-task/task/v3/internal/fingerprint:
+    interfaces:
+      SourcesCheckable:
+      StatusCheckable:

.nvmrc

@@ -1 +1 @@
-18.12.1
+22.17.1

.taskrc.yml

@@ -0,0 +1,4 @@
+experiments:
+  GENTLE_FORCE: 0
+  REMOTE_TASKFILES: 0
+  ENV_PRECEDENCE: 0

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+  "recommendations": [
+    "editorconfig.editorconfig",
+    "golang.go",
+    "task.vscode-task"
+  ]
+}

.vscode/settings-sample.json

@@ -1,5 +1,17 @@
 {
   "yaml.schemas": {
-    "./docs/static/schema.json": "Taskfile.yml"
-  }
+    "./website/static/schema.json": [
+      "Taskfile.yml",
+      "tmp/**/*.yml"
+    ]
+  },
+  "search.exclude": {
+    "**/versioned_docs": true,
+    "**/versioned_sidesbars": true,
+    "**/i18n": true
+  },
+  "gopls": {
+      "formatting.local": "github.com/go-task"
+  },
+  "go.formatTool": "gofumpt"
 }

CHANGELOG.md

@@ -1,5 +1,414 @@
 # Changelog
 
+## v3.44.1 - 2025-07-23
+
+- Internal tasks will no longer be shown as suggestions since they cannot be
+  called (#2309, #2323 by @maxmzkrcensys)
+- Fixed install script for some ARM platforms (#1516, #2291 by @trulede).
+- Fixed a regression where fingerprinting was not working correctly if the path
+  to you Taskfile contained a space (#2321, #2322 by @pd93).
+- Reverted a breaking change to `randInt` (#2312, #2316 by @pd93).
+- Made new variables `TEST_NAME` and `TEST_DIR` available in fixture tests
+  (#2265 by @pd93).
+
+## v3.44.0 - 2025-06-08
+
+- Added `uuid`, `randInt` and `randIntN` template functions (#1346, #2225 by
+  @pd93).
+- Added new `CLI_ARGS_LIST` array variable which contains the arguments passed
+  to Task after the `--` (the same as `CLI_ARGS`, but an array instead of a
+  string). (#2138, #2139, #2140 by @pd93).
+- Added `toYaml` and `fromYaml` templating functions (#2217, #2219 by @pd93).
+- Added `task` field the `--list --json` output (#2256 by @aleksandersh).
+- Added the ability to
+  [pin included taskfiles](https://taskfile.dev/next/experiments/remote-taskfiles/#manual-checksum-pinning)
+  by specifying a checksum. This works with both local and remote Taskfiles
+  (#2222, #2223 by @pd93).
+- When using the
+  [Remote Taskfiles experiment](https://github.com/go-task/task/issues/1317),
+  any credentials used in the URL will now be redacted in Task's output (#2100,
+  #2220 by @pd93).
+- Fixed fuzzy suggestions not working when misspelling a task name (#2192, #2200
+  by @vmaerten).
+- Fixed a bug where taskfiles in directories containing spaces created
+  directories in the wrong location (#2208, #2216 by @pd93).
+- Added support for dual JSON schema files, allowing changes without affecting
+  the current schema. The current schemas will only be updated during releases.
+  (#2211 by @vmaerten).
+- Improved fingerprint documentation by specifying that the method can be set at
+  the root level to apply to all tasks (#2233 by @vmaerten).
+- Fixed some watcher regressions after #2048 (#2199, #2202, #2241, #2196 by
+  @wazazaby, #2271 by @andreynering).
+
+## v3.43.3 - 2025-04-27
+
+Reverted the changes made in #2113 and #2186 that affected the
+`USER_WORKING_DIR` and built-in variables. This fixes #2206, #2195, #2207 and
+#2208.
+
+## v3.43.2 - 2025-04-21
+
+- Fixed regresion of `CLI_ARGS` being exposed as the wrong type (#2190, #2191 by
+  @vmaerten).
+
+## v3.43.1 - 2025-04-21
+
+- Significant improvements were made to the watcher. We migrated from
+  [watcher](https://github.com/radovskyb/watcher) to
+  [fsnotify](https://github.com/fsnotify/fsnotify). The former library used
+  polling, which means Task had a high CPU usage when watching too many files.
+  `fsnotify` uses proper the APIs from each operating system to watch files,
+  which means a much better performance. The default interval changed from 5
+  seconds to 100 milliseconds, because now it configures the wait time for
+  duplicated events, instead of the polling time (#2048 by @andreynering, #1508,
+  #985, #1179).
+- The [Map Variables experiment](https://github.com/go-task/task/issues/1585)
+  was made generally available so you can now
+  [define map variables in your Taskfiles!](https://taskfile.dev/usage/#variables)
+  (#1585, #1547, #2081 by @pd93).
+- Wildcards can now
+  [match multiple tasks](https://taskfile.dev/usage/#wildcard-arguments) (#2072,
+  #2121 by @pd93).
+- Added the ability to
+  [loop over the files specified by the `generates` keyword](https://taskfile.dev/usage/#looping-over-your-tasks-sources-or-generated-files).
+  This works the same way as looping over sources (#2151 by @sedyh).
+- Added the ability to resolve variables when defining an include variable
+  (#2108, #2113 by @pd93).
+- A few changes have been made to the
+  [Remote Taskfiles experiment](https://github.com/go-task/task/issues/1317)
+  (#1402, #2176 by @pd93):
+  - Cached files are now prioritized over remote ones.
+  - Added an `--expiry` flag which sets the TTL for a remote file cache. By
+    default the value will be 0 (caching disabled). If Task is running in
+    offline mode or fails to make a connection, it will fallback on the cache.
+- `.taskrc` files can now be used from subdirectories and will be searched for
+  recursively up the file tree in the same way that Taskfiles are (#2159, #2166
+  by @pd93).
+- The default taskfile (output when using the `--init` flag) is now an embedded
+  file in the binary instead of being stored in the code (#2112 by @pd93).
+- Improved the way we report the Task version when using the `--version` flag or
+  `{{.TASK_VERSION}}` variable. This should now be more consistent and easier
+  for package maintainers to use (#2131 by @pd93).
+- Fixed a bug where globstar (`**`) matching in `sources` only resolved the
+  first result (#2073, #2075 by @pd93).
+- Fixed a bug where sorting tasks by "none" would use the default sorting
+  instead of leaving tasks in the order they were defined (#2124, #2125 by
+  @trulede).
+- Fixed Fish completion on newer Fish versions (#2130 by @atusy).
+- Fixed a bug where undefined/null variables resolved to an empty string instead
+  of `nil` (#1911, #2144 by @pd93).
+- The `USER_WORKING_DIR` special now will now properly account for the `--dir`
+  (`-d`) flag, if given (#2102, #2103 by @jaynis, #2186 by @andreynering).
+- Fix Fish completions when `--global` (`-g`) is given (#2134 by @atusy).
+- Fixed variables not available when using `defer:` (#1909, #2173 by @vmaerten).
+
+#### Package API
+
+- The [`Executor`](https://pkg.go.dev/github.com/go-task/task/v3#Executor) now
+  uses the functional options pattern (#2085, #2147, #2148 by @pd93).
+- The functional options for the
+  [`taskfile.Reader`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader)
+  and
+  [`taskfile.Snippet`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Snippet)
+  types no longer have the `Reader`/`Snippet` respective prefixes (#2148 by
+  @pd93).
+- [`taskfile.Reader`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader)
+  no longer accepts a
+  [`taskfile.Node`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Node).
+  Instead nodes are passed directly into the
+  [`Reader.Read`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader.Read)
+  method (#2169 by @pd93).
+- [`Reader.Read`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader.Read)
+  also now accepts a [`context.Context`](https://pkg.go.dev/context#Context)
+  (#2176 by @pd93).
+
+## v3.42.1 - 2025-03-10
+
+- Fixed a bug where some special variables caused a type error when used global
+  variables (#2106, #2107 by @pd93).
+
+## v3.42.0 - 2025-03-08
+
+- Made `--init` less verbose by default and respect `--silent` and `--verbose`
+  flags (#2009, #2011 by @HeCorr).
+- `--init` now accepts a file name or directory as an argument (#2008, #2018 by
+  @HeCorr).
+- Fix a bug where an HTTP node's location was being mutated incorrectly (#2007
+  by @jeongukjae).
+- Fixed a bug where allowed values didn't work with dynamic var (#2032, #2033 by
+  @vmaerten).
+- Use only the relevant checker (timestamp or checksum) to improve performance
+  (#2029, #2031 by @vmaerten).
+- Print warnings when attempting to enable an inactive experiment or an active
+  experiment with an invalid value (#1979, #2049 by @pd93).
+- Refactored the experiments package and added tests (#2049 by @pd93).
+- Show allowed values when a variable with an enum is missing (#2027, #2052 by
+  @vmaerten).
+- Refactored how snippets in error work and added tests (#2068 by @pd93).
+- Fixed a bug where errors decoding commands were sometimes unhelpful (#2068 by
+  @pd93).
+- Fixed a bug in the Taskfile schema where `defer` statements in the shorthand
+  `cmds` syntax were not considered valid (#2068 by @pd93).
+- Refactored how task sorting functions work (#1798 by @pd93).
+- Added a new `.taskrc.yml` (or `.taskrc.yaml`) file to let users enable
+  experiments (similar to `.env`) (#1982 by @vmaerten).
+- Added new [Getting Started docs](https://taskfile.dev/getting-started) (#2086
+  by @pd93).
+- Allow `matrix` to use references to other variables (#2065, #2069 by @pd93).
+- Fixed a bug where, when a dynamic variable is provided, even if it is not
+  used, all other variables become unavailable in the templating system within
+  the include (#2092 by @vmaerten).
+
+#### Package API
+
+Unlike our CLI tool,
+[Task's package API is not currently stable](https://taskfile.dev/reference/package).
+In an effort to ease the pain of breaking changes for our users, we will be
+providing changelogs for our package API going forwards. The hope is that these
+changes will provide a better long-term experience for our users and allow to
+stabilize the API in the future. #121 now tracks this piece of work.
+
+- Bumped the minimum required Go version to 1.23 (#2059 by @pd93).
+- [`task.InitTaskfile`](https://pkg.go.dev/github.com/go-task/task/v3#InitTaskfile)
+  (#2011, ff8c913 by @HeCorr and @pd93)
+  - No longer accepts an `io.Writer` (output is now the caller's
+    responsibility).
+  - The path argument can now be a filename OR a directory.
+  - The function now returns the full path of the generated file.
+- [`TaskfileDecodeError.WithFileInfo`](https://pkg.go.dev/github.com/go-task/task/v3/errors#TaskfileDecodeError.WithFileInfo)
+  now accepts a string instead of the arguments required to generate a snippet
+  (#2068 by @pd93).
+  - The caller is now expected to create the snippet themselves (see below).
+- [`TaskfileSnippet`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Snippet)
+  and related code moved from the `errors` package to the `taskfile` package
+  (#2068 by @pd93).
+- Renamed `TaskMissingRequiredVars` to
+  [`TaskMissingRequiredVarsError`](https://pkg.go.dev/github.com/go-task/task/v3/errors#TaskMissingRequiredVarsError)
+  (#2052 by @vmaerten).
+- Renamed `TaskNotAllowedVars` to
+  [`TaskNotAllowedVarsError`](https://pkg.go.dev/github.com/go-task/task/v3/errors#TaskNotAllowedVarsError)
+  (#2052 by @vmaerten).
+- The
+  [`taskfile.Reader`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader)
+  is now constructed using the functional options pattern (#2082 by @pd93).
+- Removed our internal `logger.Logger` from the entire `taskfile` package (#2082
+  by @pd93).
+  - Users are now expected to pass a custom debug/prompt functions into
+    [`taskfile.Reader`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#Reader)
+    if they want this functionality by using the new
+    [`WithDebugFunc`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#WithDebugFunc)
+    and
+    [`WithPromptFunc`](https://pkg.go.dev/github.com/go-task/task/v3/taskfile#WithPromptFunc)
+    functional options.
+- Remove `Range` functions in the `taskfile/ast` package in favour of new
+  iterator functions (#1798 by @pd93).
+- `ast.Call` was moved from the `taskfile/ast` package to the main `task`
+  package (#2084 by @pd93).
+- `ast.Tasks.FindMatchingTasks` was moved from the `taskfile/ast` package to the
+  `task.Executor.FindMatchingTasks` in the main `task` package (#2084 by @pd93).
+- The `Compiler` and its `GetVariables` and `FastGetVariables` methods were
+  moved from the `internal/compiler` package to the main `task` package (#2084
+  by @pd93).
+
+## v3.41.0 - 2025-01-18
+
+- Fixed an issue where dynamic variables were not properly logged in verbose
+  mode (#1920, #1921 by @mgbowman).
+- Support `silent` for defer statements (#1877, #1879 by @danilobuerger).
+- Added an option to exclude some tasks from being included (#1859 by
+  @vmaerten).
+- Fixed an issue where a required variable was incorrectly handled in a template
+  function (#1950, #1962 by @vmaerten).
+- Expose a new `TASK_DIR` special variable, which will contain the absolute path
+  of task directory. (#1959, #1961 by @vmaerten).
+- Fixed fatal bugs that caused concurrent map writes (#1605, #1972, #1974 by
+  @pd93, @GrahamDennis and @trim21).
+- Refactored internal ordered map implementation to use
+  [github.com/elliotchance/orderedmap](https://github.com/elliotchance/orderedmap)
+  (#1797 by @pd93).
+- Fixed a bug where variables defined at the task level were being ignored in
+  the `requires` section. (#1960, #1955, #1768 by @vmaerten and @mokeko)
+- The `CHECKSUM` and `TIMESTAMP` variables are now accessible within `cmds`
+  (#1872 by @niklasr22).
+- Updated [installation docs](https://taskfile.dev/installation) and added pip
+  installation method (#935, #1989 by @pd93).
+- Fixed a bug where dynamic variables could not access environment variables
+  (#630, #1869 by @rohm1 and @pd93).
+- Disable version check for use as an external library (#1938 by @leaanthony).
+
+## v3.40.1 - 2024-12-06
+
+- Fixed a security issue in `git-urls` by switching to the maintained fork
+  `chainguard-dev/git-urls` (#1917 by @AlekSi).
+- Added missing `platforms` property to `cmds` that use `for` (#1915 by
+  @dkarter).
+- Added misspell linter to check for misspelled English words (#1883 by
+  @christiandins).
+
+## v3.40.0 - 2024-11-05
+
+- Fixed output of some functions (e.g. `splitArgs`/`splitLines`) not working in
+  for loops (#1822, #1823 by @stawii).
+- Added a new `TASK_OFFLINE` environment variable to configure the `--offline`
+  flag and expose it as a special variable in the templating system (#1470,
+  #1716 by @vmaerten and @pd93).
+- Fixed a bug where multiple remote includes caused all prompts to display
+  without waiting for user input (#1832, #1833 by @vmaerten and @pd93).
+- When using the
+  "[Remote Taskfiles](https://taskfile.dev/experiments/remote-taskfiles/)".
+  experiment, you can now include Taskfiles from Git repositories (#1652 by
+  @vmaerten).
+- Improved the error message when a dotenv file cannot be parsed (#1842 by
+  @pbitty).
+- Fix issue with directory when using the remote experiment (#1757 by @pbitty).
+- Fixed an issue where a special variable was used in combination with a dotenv
+  file (#1232, #1810 by @vmaerten).
+- Refactor the way Task reads Taskfiles to improve readability (#1771 by
+  @pbitty).
+- Added a new option to ensure variable is within the list of values (#1827 by
+  @vmaerten).
+- Allow multiple prompts to be specified for a task (#1861, #1866 by @mfbmina).
+- Added new template function: `numCPU`, which returns the number of logical
+  CPUs usable (#1890, #1887 by @Amoghrd).
+- Fixed a bug where non-nil, empty dynamic variables are returned as an empty
+  interface (#1903, #1904 by @pd93).
+
+## v3.39.2 - 2024-09-19
+
+- Fix dynamic variables not working properly for a defer: statement (#1803,
+  #1818 by @vmaerten).
+
+## v3.39.1 - 2024-09-18
+
+- Added Renovate configuration to automatically create PRs to keep dependencies
+  up to date (#1783 by @vmaerten).
+- Fixed a bug where the help was displayed twice (#1805, #1806 by @vmaerten).
+- Fixed a bug where ZSH and PowerShell completions did not work when using the
+  recommended method. (#1813, #1809 by @vmaerten and @shirayu)
+- Fix variables not working properly for a `defer:` statement (#1803, #1814 by
+  @vmaerten and @andreynering).
+
+## v3.39.0 - 2024-09-07
+
+- Added
+  [Env Precedence Experiment](https://taskfile.dev/experiments/env-precedence)
+  (#1038, #1633 by @vmaerten).
+- Added a CI lint job to ensure that the docs are updated correctly (#1719 by
+  @vmaerten).
+- Updated minimum required Go version to 1.22 (#1758 by @pd93).
+- Expose a new `EXIT_CODE` special variable on `defer:` when a command finishes
+  with a non-zero exit code (#1484, #1762 by @dorimon-1 and @andreynering).
+- Expose a new `ALIAS` special variable, which will contain the alias used to
+  call the current task. Falls back to the task name. (#1764 by @DanStory).
+- Fixed `TASK_REMOTE_DIR` environment variable not working when the path was
+  absolute. (#1715 by @vmaerten).
+- Added an option to declare an included Taskfile as flattened (#1704 by
+  @vmaerten).
+- Added a new
+  [`--completion` flag](https://taskfile.dev/installation/#setup-completions) to
+  output completion scripts for various shells (#293, #1157 by @pd93).
+  - This is now the preferred way to install completions.
+  - The completion scripts in the `completion` directory
+    [are now deprecated](https://taskfile.dev/deprecations/completion-scripts/).
+- Added the ability to
+  [loop over a matrix of values](https://taskfile.dev/usage/#looping-over-a-matrix)
+  (#1766, #1767, #1784 by @pd93).
+- Fixed a bug in fish completion where aliases were not displayed (#1781, #1782
+  by @vmaerten).
+- Fixed panic when having a flattened included Taskfile that contains a
+  `default` task (#1777, #1778 by @vmaerten).
+- Optimized file existence checks for remote Taskfiles (#1713 by @vmaerten).
+
+## v3.38.0 - 2024-06-30
+
+- Added `TASK_EXE` special variable (#1616, #1624 by @pd93 and @andreynering).
+- Some YAML parsing errors will now show in a more user friendly way (#1619 by
+  @pd93).
+- Prefixed outputs will now be colorized by default (#1572 by
+  @AlexanderArvidsson)
+- [References](https://taskfile.dev/usage/#referencing-other-variables) are now
+  generally available (no experiments required) (#1654 by @pd93).
+- Templating functions can now be used in references (#1645, #1654 by @pd93).
+- Added a new
+  [templating reference page](https://taskfile.dev/reference/templating/) to the
+  documentation (#1614, #1653 by @pd93).
+- If using the
+  [Map Variables experiment (1)](https://taskfile.dev/experiments/map-variables/?proposal=1),
+  references are available by
+  [prefixing a string with a `#`](https://taskfile.dev/experiments/map-variables/?proposal=1#references)
+  (#1654 by @pd93).
+- If using the
+  [Map Variables experiment (2)](https://taskfile.dev/experiments/map-variables/?proposal=2),
+  the `yaml` and `json` keys are no longer available (#1654 by @pd93).
+- Added a new `TASK_REMOTE_DIR` environment variable to configure where cached
+  remote Taskfiles are stored (#1661 by @vmaerten).
+- Added a new `--clear-cache` flag to clear the cache of remote Taskfiles (#1639
+  by @vmaerten).
+- Improved the readability of cached remote Taskfile filenames (#1636 by
+  @vmaerten).
+- Starting releasing a binary for the `riscv64` architecture on Linux (#1699 by
+  @mengzhuo).
+- Added `CLI_SILENT` and `CLI_VERBOSE` variables (#1480, #1669 by @Vince-Smith).
+- Fixed a couple of bugs with the `prompt:` feature (#1657 by @pd93).
+- Fixed JSON Schema to disallow invalid properties (#1657 by @pd93).
+- Fixed version checks not working as intended (#872, #1663 by @vmaerten).
+- Fixed a bug where included tasks were run multiple times even if `run: once`
+  was set (#852, #1655 by @pd93).
+- Fixed some bugs related to column formatting in the terminal (#1350, #1637,
+  #1656 by @vmaerten).
+
+## v3.37.2 - 2024-05-12
+
+- Fixed a bug where an empty Taskfile would cause a panic (#1648 by @pd93).
+- Fixed a bug where includes Taskfile variable were not being merged correctly
+  (#1643, #1649 by @pd93).
+
+## v3.37.1 - 2024-05-09
+
+- Fix bug where non-string values (numbers, bools) added to `env:` weren't been
+  correctly exported (#1640, #1641 by @vmaerten and @andreynering).
+
+## v3.37.0 - 2024-05-08
+
+- Released the
+  [Any Variables experiment](https://taskfile.dev/blog/any-variables), but
+  [_without support for maps_](https://github.com/go-task/task/issues/1415#issuecomment-2044756925)
+  (#1415, #1547 by @pd93).
+- Refactored how Task reads, parses and merges Taskfiles using a DAG (#1563,
+  #1607 by @pd93).
+- Fix a bug which stopped tasks from using `stdin` as input (#1593, #1623 by
+  @pd93).
+- Fix error when a file or directory in the project contained a special char
+  like `&`, `(` or `)` (#1551, #1584 by @andreynering).
+- Added alias `q` for template function `shellQuote` (#1601, #1603 by @vergenzt)
+- Added support for `~` on ZSH completions (#1613 by @jwater7).
+- Added the ability to pass variables by reference using Go template syntax when
+  the
+  [Map Variables experiment](https://taskfile.dev/experiments/map-variables/) is
+  enabled (#1612 by @pd93).
+- Added support for environment variables in the templating engine in `includes`
+  (#1610 by @vmaerten).
+
+## v3.36.0 - 2024-04-08
+
+- Added support for
+  [looping over dependencies](https://taskfile.dev/usage/#looping-over-dependencies)
+  (#1299, #1541 by @pd93).
+- When using the
+  "[Remote Taskfiles](https://taskfile.dev/experiments/remote-taskfiles/)"
+  experiment, you are now able to use
+  [remote Taskfiles as your entrypoint](https://taskfile.dev/experiments/remote-taskfiles/#root-remote-taskfiles).
+  - `includes` in remote Taskfiles will now also resolve correctly (#1347 by
+    @pd93).
+- When using the
+  "[Any Variables](https://taskfile.dev/experiments/any-variables/)"
+  experiments, templating is now supported in collection-type variables (#1477,
+  #1511, #1526 by @pd93).
+- Fixed a bug where variables being passed to an included Taskfile were not
+  available when defining global variables (#1503, #1533 by @pd93).
+- Improved support to customized colors by allowing 8-bit colors and multiple
+  ANSI attributes (#1576 by @pd93).
+
 ## v3.35.1 - 2024-03-04
 
 - Fixed a bug where the `TASKFILE_DIR` variable was sometimes incorrect (#1522,
@@ -128,8 +537,8 @@
 - Added the
   [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles)
   as a draft (#1152, #1317 by @pd93).
-- Improve performance of content checksuming on `sources:` by replacing md5 with
-  [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking
+- Improve performance of content checksumming on `sources:` by replacing md5
+  with [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking
   change because checksums will be invalidated when upgrading to this release
   (#1325 by @ReillyBrogan).
 
@@ -188,7 +597,7 @@
 - Deprecated `version: 2` schema. This will be removed in the next major release
   (#1197, #1198, #1199 by @pd93).
 - Added a new `prompt:` prop to set a warning prompt to be shown before running
-  a potential dangurous task (#100, #1163 by @MaxCheetham,
+  a potential dangerous task (#100, #1163 by @MaxCheetham,
   [Documentation](https://taskfile.dev/usage/#warning-prompts)).
 - Added support for single command task syntax. With this change, it's now
   possible to declare just `cmd:` in a task, avoiding the more complex
@@ -203,7 +612,7 @@
   percentage (#1173 by @misitebao).
 - Starting on this release, official binaries for FreeBSD will be available to
   download (#1068 by @andreynering).
-- Fix some errors being unintendedly supressed (#1134 by @clintmod).
+- Fix some errors being unintendedly suppressed (#1134 by @clintmod).
 - Fix a nil pointer error when `version` is omitted from a Taskfile (#1148,
   #1149 by @pd93).
 - Fix duplicate error message when a task does not exists (#1141, #1144 by
@@ -276,8 +685,8 @@ it a go and let us know what you think via a
 - Fixed a bug where tasks were sometimes incorrectly marked as internal (#1007
   by @pd93).
 - Update to Go 1.20 (bump minimum version to 1.19) (#1010 by @pd93)
-- Added environment variable `FORCE_COLOR` support to force color output.
-  Usefull for environments without TTY (#1003 by @automation-stack)
+- Added environment variable `FORCE_COLOR` support to force color output. Useful
+  for environments without TTY (#1003 by @automation-stack)
 
 ## v3.20.0 - 2023-01-14
 
@@ -632,7 +1041,7 @@ it a go and let us know what you think via a
 
 - Fix error code for the `--help` flag (#300, #330).
 - Print version to stdout instead of stderr (#299, #329).
-- Supress `context` errors when using the `--watch` flag (#313, #317).
+- Suppress `context` errors when using the `--watch` flag (#313, #317).
 - Support templating on description (#276, #283).
 
 ## v2.8.0 - 2019-12-07
@@ -641,7 +1050,7 @@ it a go and let us know what you think via a
   parallel (#266).
 - Fixed bug where calling the `task` CLI only informing global vars would not
   execute the `default` task.
-- Add hability to silent all tasks by adding `silent: true` a the root of the
+- Add ability to silent all tasks by adding `silent: true` a the root of the
   Taskfile.
 
 ## v2.7.1 - 2019-11-10
@@ -783,7 +1192,7 @@ document, since it describes in depth what changed for this version.
 ## v1.4.3 - 2017-09-07
 
 - Allow assigning variables to tasks at run time via CLI (#33)
-- Added suport for multiline variables from sh (#64)
+- Added support for multiline variables from sh (#64)
 - Fixes env: remove square braces and evaluate shell (#62)
 - Watch: change watch library and few fixes and improvements
 - When use watching, cancel and restart long running process on file change (#59
@@ -843,7 +1252,7 @@ document, since it describes in depth what changed for this version.
 - More tests and Travis integration
 - Watch a task (experimental)
 - Possibility to call another task
-- Fix "=" not being reconized in variables/environment variables
+- Fix "=" not being recognized in variables/environment variables
 - Tasks can now have a description, and help will print them (#10)
 - Task dependencies now run concurrently
 - Support for a default task (#16)

README.md

@@ -1,6 +1,6 @@
 <div align="center">
   <a href="https://taskfile.dev">
-    <img src="docs/static/img/logo.svg" width="200px" height="200px" />
+    <img src="website/static/img/logo.svg" width="200px" height="200px" />
   </a>
 
   <h1>Task</h1>
@@ -10,6 +10,18 @@
   </p>
 
   <p>
-    <a href="https://taskfile.dev/installation/">Installation</a> | <a href="https://taskfile.dev/usage/">Documentation</a> | <a href="https://twitter.com/taskfiledev">Twitter</a> | <a href="https://fosstodon.org/@task">Mastodon</a> | <a href="https://discord.gg/6TY36E39UK">Discord</a>
+    <a href="https://taskfile.dev/installation/">Installation</a> | <a href="https://taskfile.dev/usage/">Documentation</a> | <a href="https://twitter.com/taskfiledev">Twitter</a> | <a href="https://bsky.app/profile/taskfile.dev">Bluesky</a> | <a href="https://fosstodon.org/@task">Mastodon</a> | <a href="https://discord.gg/6TY36E39UK">Discord</a>
   </p>
+
+  <h1>Gold Sponsors</h1>
+
+  <table>
+    <tr>
+      <td align="center" valign="middle">
+        <a target="_blank" href="https://devowl.io">
+          <img src="/website/static/img/devowl.io.svg" height="100px" title="devowl.io" />
+        </a>
+      </td>
+    </tr>
+  </table>
 </div>

Taskfile.yml

@@ -1,10 +1,10 @@
 version: '3'
 
 includes:
-  docs:
-    aliases: [d]
-    taskfile: ./docs
-    dir: ./docs
+  website:
+    aliases: [w, docs, d]
+    taskfile: ./website
+    dir: ./website
 
 vars:
   BIN: "{{.ROOT_DIR}}/bin"
@@ -18,6 +18,11 @@ tasks:
       - task: lint
       - task: test
 
+  run:
+    desc: Runs Task
+    cmds:
+      - go run ./cmd/task {{.CLI_ARGS}}
+
   install:
     desc: Installs Task
     aliases: [i]
@@ -27,27 +32,44 @@ tasks:
       - go install -v ./cmd/task
 
   generate:
-    desc: Runs Go generate to create mocks
     aliases: [gen, g]
+    desc: Runs all generate tasks
+    cmds:
+      - task: generate:mocks
+      - task: generate:fixtures
+
+  generate:mocks:
+    desc: Runs Mockery to create mocks
+    aliases: [gen:mocks, g:mocks]
     deps: [install:mockery]
     sources:
       - "internal/fingerprint/checker.go"
     generates:
       - "internal/mocks/*.go"
     cmds:
-      - "{{.BIN}}/mockery --dir ./internal/fingerprint --name SourcesCheckable"
-      - "{{.BIN}}/mockery --dir ./internal/fingerprint --name StatusCheckable"
+      - find . -type f -name *_mock.go -delete
+      - "{{.BIN}}/mockery"
+
+  generate:fixtures:
+    desc: Runs tests and generates golden fixture files
+    aliases: [gen:fixtures, g:fixtures]
+    env:
+      GOLDIE_UPDATE: 'true'
+      GOLDIE_TEMPLATE: 'true'
+    cmds:
+      - find ./testdata -name '*.golden' -delete
+      - go test ./...
 
   install:mockery:
     desc: Installs mockgen; a tool to generate mock files
     vars:
-      MOCKERY_VERSION: v2.24.0
+      MOCKERY_VERSION: v3.2.2
     env:
       GOBIN: "{{.BIN}}"
     status:
       - go version -m {{.BIN}}/mockery | grep github.com/vektra/mockery | grep {{.MOCKERY_VERSION}}
     cmds:
-      - go install github.com/vektra/mockery/v2@{{.MOCKERY_VERSION}}
+      - GOBIN="{{.BIN}}" go install github.com/vektra/mockery/v3@{{.MOCKERY_VERSION}}
 
   mod:
     desc: Downloads and tidy Go modules
@@ -57,6 +79,7 @@ tasks:
 
   clean:
     desc: Cleans temp files and folders
+    aliases: [clear]
     cmds:
       - rm -rf dist/
       - rm -rf tmp/
@@ -67,6 +90,7 @@ tasks:
     sources:
       - './**/*.go'
       - .golangci.yml
+      - go.mod
     cmds:
       - golangci-lint run
 
@@ -75,9 +99,19 @@ tasks:
     sources:
       - './**/*.go'
       - .golangci.yml
+      - go.mod
     cmds:
       - golangci-lint run --fix
 
+  format:
+    desc: Runs golangci-lint and formats any Go files
+    aliases: [fmt, f]
+    sources:
+      - './**/*.go'
+      - .golangci.yml
+    cmds:
+      - golangci-lint fmt
+
   sleepit:build:
     desc: Builds the sleepit test helper
     sources:
@@ -97,21 +131,23 @@ tasks:
   test:
     desc: Runs test suite
     aliases: [t]
-    deps: [install]
+    sources:
+      - "**/*.go"
+      - "testdata/**/*"
     cmds:
-      - go test {{catLines .GO_PACKAGES}}
-    vars:
-      GO_PACKAGES:
-        sh: go list ./...
+      - go test ./...
+
+  test:watch:
+    desc: Runs test suite with watch tests included
+    deps: [sleepit:build]
+    cmds:
+      - go test ./... -tags 'watch'
 
   test:all:
     desc: Runs test suite with signals and watch tests included
-    deps: [install, sleepit:build]
+    deps: [sleepit:build]
     cmds:
-      - go test {{catLines .GO_PACKAGES}} -tags 'signals watch'
-    vars:
-      GO_PACKAGES:
-        sh: go list ./...
+      - go test -tags 'signals watch' ./...
 
   goreleaser:test:
     desc: Tests release process without publishing
@@ -121,22 +157,73 @@ tasks:
   goreleaser:install:
     desc: Installs goreleaser
     cmds:
-      - go install github.com/goreleaser/goreleaser@latest
+      - go install github.com/goreleaser/goreleaser/v2@latest
 
-  release:
-    desc: Prepare the project for a new release
+  gorelease:install:
+    desc: "Installs gorelease: https://pkg.go.dev/golang.org/x/exp/cmd/gorelease"
+    status:
+      - command -v gorelease
     cmds:
-      - go run ./cmd/release {{.CLI_ARGS}}
+      - go install golang.org/x/exp/cmd/gorelease@latest
+
+  api:check:
+    desc: Checks what changes have been made to the public API
+    deps: [gorelease:install]
+    vars:
+      LATEST:
+        sh: git describe --tags --abbrev=0
+    cmds:
+      - gorelease -base={{.LATEST}}
+
+  release:*:
+    desc: Prepare the project for a new release
+    summary: |
+      This task will do the following:
+
+      - Update the version and date in the CHANGELOG.md file
+      - Update the version in the package.json and package-lock.json files
+      - Copy the latest docs to the "current" version on the website
+      - Commit the changes
+      - Create a new tag
+      - Push the commit/tag to the repository
+      - Create a GitHub release
+
+      To use the task, run "task release:<version>" where "<version>" is is one of:
+
+      - "major" - Bumps the major number
+      - "minor" - Bumps the minor number
+      - "patch" - Bumps the patch number
+      - A semver compatible version number (e.g. "1.2.3")
+    vars:
+      VERSION:
+        sh: "go run ./cmd/release --version {{index .MATCH 0}}"
+      COMPLETE_MESSAGE: |
+        Creating release with GoReleaser: https://github.com/go-task/task/actions/workflows/release.yml
+
+        Please wait for the CI to finish and then do the following:
+
+        - Copy the changelog for v{{.VERSION}} to the GitHub release
+        - Publish the package to NPM with `task npm:publish`
+        - Update and push the snapcraft manifest in https://github.com/go-task/snap/blob/main/snap/snapcraft.yaml
+    preconditions:
+      - sh: test $(git rev-parse --abbrev-ref HEAD) = "main"
+        msg: "You must be on the main branch to release"
+      - sh: "[[ -z $(git diff --shortstat main) ]]"
+        msg: "You must have a clean working tree to release"
+    prompt: "Are you sure you want to release version {{.VERSION}}?"
+    cmds:
+      - cmd: echo "Releasing v{{.VERSION}}"
+        silent: true
+      - "go run ./cmd/release {{.VERSION}}"
+      - "git add --all"
+      - "git commit -m v{{.VERSION}}"
+      - "git push"
+      - "git tag v{{.VERSION}}"
+      - "git push origin tag v{{.VERSION}}"
+      - cmd: printf "%s" '{{.COMPLETE_MESSAGE}}'
+        silent: true
 
   npm:publish:
     desc: Publish release to npm
     cmds:
       - npm publish --access=public
-
-  packages:
-    cmds:
-      - echo '{{.GO_PACKAGES}}'
-    vars:
-      GO_PACKAGES:
-        sh: go list ./...
-    silent: true

args/args.go

@@ -3,17 +3,34 @@ package args
 import (
 	"strings"
 
+	"github.com/spf13/pflag"
+	"mvdan.cc/sh/v3/syntax"
+
+	"github.com/go-task/task/v3"
 	"github.com/go-task/task/v3/taskfile/ast"
 )
 
+// Get fetches the remaining arguments after CLI parsing and splits them into
+// two groups: the arguments before the double dash (--) and the arguments after
+// the double dash.
+func Get() ([]string, []string, error) {
+	args := pflag.Args()
+	doubleDashPos := pflag.CommandLine.ArgsLenAtDash()
+
+	if doubleDashPos == -1 {
+		return args, nil, nil
+	}
+	return args[:doubleDashPos], args[doubleDashPos:], nil
+}
+
 // Parse parses command line argument: tasks and global variables
-func Parse(args ...string) ([]*ast.Call, *ast.Vars) {
-	calls := []*ast.Call{}
-	globals := &ast.Vars{}
+func Parse(args ...string) ([]*task.Call, *ast.Vars) {
+	calls := []*task.Call{}
+	globals := ast.NewVars()
 
 	for _, arg := range args {
 		if !strings.Contains(arg, "=") {
-			calls = append(calls, &ast.Call{Task: arg})
+			calls = append(calls, &task.Call{Task: arg})
 			continue
 		}
 
@@ -24,6 +41,18 @@ func Parse(args ...string) ([]*ast.Call, *ast.Vars) {
 	return calls, globals
 }
 
+func ToQuotedString(args []string) (string, error) {
+	var quotedCliArgs []string
+	for _, arg := range args {
+		quotedCliArg, err := syntax.Quote(arg, syntax.LangBash)
+		if err != nil {
+			return "", err
+		}
+		quotedCliArgs = append(quotedCliArgs, quotedCliArg)
+	}
+	return strings.Join(quotedCliArgs, " "), nil
+}
+
 func splitVar(s string) (string, string) {
 	pair := strings.SplitN(s, "=", 2)
 	return pair[0], pair[1]

args/args_test.go

@@ -6,20 +6,22 @@ import (
 
 	"github.com/stretchr/testify/assert"
 
+	"github.com/go-task/task/v3"
 	"github.com/go-task/task/v3/args"
-	"github.com/go-task/task/v3/internal/omap"
 	"github.com/go-task/task/v3/taskfile/ast"
 )
 
 func TestArgs(t *testing.T) {
+	t.Parallel()
+
 	tests := []struct {
 		Args            []string
-		ExpectedCalls   []*ast.Call
+		ExpectedCalls   []*task.Call
 		ExpectedGlobals *ast.Vars
 	}{
 		{
 			Args: []string{"task-a", "task-b", "task-c"},
-			ExpectedCalls: []*ast.Call{
+			ExpectedCalls: []*task.Call{
 				{Task: "task-a"},
 				{Task: "task-b"},
 				{Task: "task-c"},
@@ -27,81 +29,98 @@ func TestArgs(t *testing.T) {
 		},
 		{
 			Args: []string{"task-a", "FOO=bar", "task-b", "task-c", "BAR=baz", "BAZ=foo"},
-			ExpectedCalls: []*ast.Call{
+			ExpectedCalls: []*task.Call{
 				{Task: "task-a"},
 				{Task: "task-b"},
 				{Task: "task-c"},
 			},
-			ExpectedGlobals: &ast.Vars{
-				OrderedMap: omap.FromMapWithOrder(
-					map[string]ast.Var{
-						"FOO": {Value: "bar"},
-						"BAR": {Value: "baz"},
-						"BAZ": {Value: "foo"},
+			ExpectedGlobals: ast.NewVars(
+				&ast.VarElement{
+					Key: "FOO",
+					Value: ast.Var{
+						Value: "bar",
 					},
-					[]string{"FOO", "BAR", "BAZ"},
-				),
-			},
+				},
+				&ast.VarElement{
+					Key: "BAR",
+					Value: ast.Var{
+						Value: "baz",
+					},
+				},
+				&ast.VarElement{
+					Key: "BAZ",
+					Value: ast.Var{
+						Value: "foo",
+					},
+				},
+			),
 		},
 		{
 			Args: []string{"task-a", "CONTENT=with some spaces"},
-			ExpectedCalls: []*ast.Call{
+			ExpectedCalls: []*task.Call{
 				{Task: "task-a"},
 			},
-			ExpectedGlobals: &ast.Vars{
-				OrderedMap: omap.FromMapWithOrder(
-					map[string]ast.Var{
-						"CONTENT": {Value: "with some spaces"},
+			ExpectedGlobals: ast.NewVars(
+				&ast.VarElement{
+					Key: "CONTENT",
+					Value: ast.Var{
+						Value: "with some spaces",
 					},
-					[]string{"CONTENT"},
-				),
-			},
+				},
+			),
 		},
 		{
 			Args: []string{"FOO=bar", "task-a", "task-b"},
-			ExpectedCalls: []*ast.Call{
+			ExpectedCalls: []*task.Call{
 				{Task: "task-a"},
 				{Task: "task-b"},
 			},
-			ExpectedGlobals: &ast.Vars{
-				OrderedMap: omap.FromMapWithOrder(
-					map[string]ast.Var{
-						"FOO": {Value: "bar"},
+			ExpectedGlobals: ast.NewVars(
+				&ast.VarElement{
+					Key: "FOO",
+					Value: ast.Var{
+						Value: "bar",
 					},
-					[]string{"FOO"},
-				),
-			},
+				},
+			),
 		},
 		{
 			Args:          nil,
-			ExpectedCalls: []*ast.Call{},
+			ExpectedCalls: []*task.Call{},
 		},
 		{
 			Args:          []string{},
-			ExpectedCalls: []*ast.Call{},
+			ExpectedCalls: []*task.Call{},
 		},
 		{
 			Args:          []string{"FOO=bar", "BAR=baz"},
-			ExpectedCalls: []*ast.Call{},
-			ExpectedGlobals: &ast.Vars{
-				OrderedMap: omap.FromMapWithOrder(
-					map[string]ast.Var{
-						"FOO": {Value: "bar"},
-						"BAR": {Value: "baz"},
+			ExpectedCalls: []*task.Call{},
+			ExpectedGlobals: ast.NewVars(
+				&ast.VarElement{
+					Key: "FOO",
+					Value: ast.Var{
+						Value: "bar",
 					},
-					[]string{"FOO", "BAR"},
-				),
-			},
+				},
+				&ast.VarElement{
+					Key: "BAR",
+					Value: ast.Var{
+						Value: "baz",
+					},
+				},
+			),
 		},
 	}
 
 	for i, test := range tests {
 		t.Run(fmt.Sprintf("TestArgs%d", i+1), func(t *testing.T) {
+			t.Parallel()
+
 			calls, globals := args.Parse(test.Args...)
 			assert.Equal(t, test.ExpectedCalls, calls)
 			if test.ExpectedGlobals.Len() > 0 || globals.Len() > 0 {
-				assert.Equal(t, test.ExpectedGlobals.Keys(), globals.Keys())
-				assert.Equal(t, test.ExpectedGlobals.Values(), globals.Values())
+				assert.Equal(t, test.ExpectedGlobals, globals)
+				assert.Equal(t, test.ExpectedGlobals, globals)
 			}
 		})
 	}

call.go

@@ -1,9 +1,11 @@
-package ast
+package task
+
+import "github.com/go-task/task/v3/taskfile/ast"
 
 // Call is the parameters to a task call
 type Call struct {
 	Task     string
-	Vars     *Vars
+	Vars     *ast.Vars
 	Silent   bool
 	Indirect bool // True if the task was called by another task
 }

cmd/release/main.go

@@ -1,7 +1,6 @@
 package main
 
 import (
-	"errors"
 	"fmt"
 	"os"
 	"os/exec"
@@ -10,11 +9,21 @@ import (
 	"time"
 
 	"github.com/Masterminds/semver/v3"
+	"github.com/otiai10/copy"
+	"github.com/spf13/pflag"
+
+	"github.com/go-task/task/v3/errors"
 )
 
 const (
-	changelogSource = "CHANGELOG.md"
-	changelogTarget = "docs/docs/changelog.md"
+	changelogSource    = "CHANGELOG.md"
+	changelogTarget    = "website/docs/changelog.mdx"
+	docsSource         = "website/docs"
+	docsTarget         = "website/versioned_docs/version-latest"
+	schemaSource       = "website/static/next-schema.json"
+	schemaTarget       = "website/static/schema.json"
+	schemaTaskrcSource = "website/static/next-schema-taskrc.json"
+	schemaTaskrcTarget = "website/static/schema-taskrc.json"
 )
 
 var (
@@ -22,6 +31,16 @@ var (
 	versionRegex          = regexp.MustCompile(`(?m)^  "version": "\d+\.\d+\.\d+",$`)
 )
 
+// Flags
+var (
+	versionFlag bool
+)
+
+func init() {
+	pflag.BoolVarP(&versionFlag, "version", "v", false, "resolved version number")
+	pflag.Parse()
+}
+
 func main() {
 	if err := release(); err != nil {
 		fmt.Println(err)
@@ -30,7 +49,7 @@ func main() {
 }
 
 func release() error {
-	if len(os.Args) != 2 {
+	if len(pflag.Args()) != 1 {
 		return errors.New("error: expected version number")
 	}
 
@@ -39,16 +58,23 @@ func release() error {
 		return err
 	}
 
-	if err := bumpVersion(version, os.Args[1]); err != nil {
+	if err := bumpVersion(version, pflag.Arg(0)); err != nil {
 		return err
 	}
 
-	fmt.Println(version)
+	if versionFlag {
+		fmt.Println(version)
+		return nil
+	}
 
 	if err := changelog(version); err != nil {
 		return err
 	}
 
+	if err := setVersionFile("internal/version/version.txt", version); err != nil {
+		return err
+	}
+
 	if err := setJSONVersion("package.json", version); err != nil {
 		return err
 	}
@@ -57,6 +83,14 @@ func release() error {
 		return err
 	}
 
+	if err := docs(); err != nil {
+		return err
+	}
+
+	if err := schema(); err != nil {
+		return err
+	}
+
 	return nil
 }
 
@@ -122,6 +156,10 @@ func changelog(version *semver.Version) error {
 	return os.WriteFile(changelogTarget, []byte(changelog), 0o644)
 }
 
+func setVersionFile(fileName string, version *semver.Version) error {
+	return os.WriteFile(fileName, []byte(version.String()+"\n"), 0o644)
+}
+
 func setJSONVersion(fileName string, version *semver.Version) error {
 	// Read the JSON file
 	b, err := os.ReadFile(fileName)
@@ -135,3 +173,23 @@ func setJSONVersion(fileName string, version *semver.Version) error {
 	// Write the JSON file
 	return os.WriteFile(fileName, []byte(new), 0o644)
 }
+
+func docs() error {
+	if err := os.RemoveAll(docsTarget); err != nil {
+		return err
+	}
+	if err := copy.Copy(docsSource, docsTarget); err != nil {
+		return err
+	}
+	return nil
+}
+
+func schema() error {
+	if err := copy.Copy(schemaSource, schemaTarget); err != nil {
+		return err
+	}
+	if err := copy.Copy(schemaTaskrcSource, schemaTaskrcTarget); err != nil {
+		return err
+	}
+	return nil
+}

cmd/sleepit/sleepit.go

@@ -159,7 +159,7 @@ func worker(
 	return workerDone
 }
 
-// Do some work and then return, so that the caller can decide wether to continue or not.
+// Do some work and then return, so that the caller can decide whether to continue or not.
 // Return true when all work is done.
 func doSomeWork(deadline time.Time) bool {
 	if time.Now().After(deadline) {

cmd/task/task.go

@@ -3,22 +3,19 @@ package main
 import (
 	"context"
 	"fmt"
-	"log"
 	"os"
 	"path/filepath"
-	"strings"
 
 	"github.com/spf13/pflag"
-	"mvdan.cc/sh/v3/syntax"
 
 	"github.com/go-task/task/v3"
 	"github.com/go-task/task/v3/args"
 	"github.com/go-task/task/v3/errors"
-	"github.com/go-task/task/v3/internal/experiments"
+	"github.com/go-task/task/v3/experiments"
+	"github.com/go-task/task/v3/internal/filepathext"
 	"github.com/go-task/task/v3/internal/flags"
 	"github.com/go-task/task/v3/internal/logger"
-	"github.com/go-task/task/v3/internal/sort"
-	ver "github.com/go-task/task/v3/internal/version"
+	"github.com/go-task/task/v3/internal/version"
 	"github.com/go-task/task/v3/taskfile/ast"
 )
 
@@ -45,18 +42,23 @@ func main() {
 }
 
 func run() error {
-	log.SetFlags(0)
-	log.SetOutput(os.Stderr)
+	log := &logger.Logger{
+		Stdout:  os.Stdout,
+		Stderr:  os.Stderr,
+		Verbose: flags.Verbose,
+		Color:   flags.Color,
+	}
 
 	if err := flags.Validate(); err != nil {
 		return err
 	}
 
-	dir := flags.Dir
-	entrypoint := flags.Entrypoint
+	if err := experiments.Validate(); err != nil {
+		log.Warnf("%s\n", err.Error())
+	}
 
 	if flags.Version {
-		fmt.Printf("Task version: %s\n", ver.GetVersion())
+		fmt.Println(version.GetVersionWithBuildInfo())
 		return nil
 	}
 
@@ -66,95 +68,71 @@ func run() error {
 	}
 
 	if flags.Experiments {
-		l := &logger.Logger{
-			Stdout:  os.Stdout,
-			Stderr:  os.Stderr,
-			Verbose: flags.Verbose,
-			Color:   flags.Color,
-		}
-		return experiments.List(l)
+		return log.PrintExperiments()
 	}
 
 	if flags.Init {
 		wd, err := os.Getwd()
 		if err != nil {
-			log.Fatal(err)
+			return err
 		}
-		if err := task.InitTaskfile(os.Stdout, wd); err != nil {
-			log.Fatal(err)
+		args, _, err := args.Get()
+		if err != nil {
+			return err
+		}
+		path := wd
+		if len(args) > 0 {
+			name := args[0]
+			if filepathext.IsExtOnly(name) {
+				name = filepathext.SmartJoin(filepath.Dir(name), "Taskfile"+filepath.Ext(name))
+			}
+			path = filepathext.SmartJoin(wd, name)
+		}
+		finalPath, err := task.InitTaskfile(path)
+		if err != nil {
+			return err
+		}
+		if !flags.Silent {
+			if flags.Verbose {
+				log.Outf(logger.Default, "%s\n", task.DefaultTaskfile)
+			}
+			log.Outf(logger.Green, "Taskfile created: %s\n", filepathext.TryAbsToRel(finalPath))
 		}
 		return nil
 	}
 
-	if flags.Global {
-		home, err := os.UserHomeDir()
+	if flags.Completion != "" {
+		script, err := task.Completion(flags.Completion)
 		if err != nil {
-			return fmt.Errorf("task: Failed to get user home directory: %w", err)
+			return err
 		}
-		dir = home
-	}
-
-	if entrypoint != "" {
-		dir = filepath.Dir(entrypoint)
-		entrypoint = filepath.Base(entrypoint)
-	}
-
-	var taskSorter sort.TaskSorter
-	switch flags.TaskSort {
-	case "none":
-		taskSorter = &sort.Noop{}
-	case "alphanumeric":
-		taskSorter = &sort.AlphaNumeric{}
-	}
-
-	e := task.Executor{
-		Dir:         dir,
-		Entrypoint:  entrypoint,
-		Force:       flags.Force,
-		ForceAll:    flags.ForceAll,
-		Insecure:    flags.Insecure,
-		Download:    flags.Download,
-		Offline:     flags.Offline,
-		Timeout:     flags.Timeout,
-		Watch:       flags.Watch,
-		Verbose:     flags.Verbose,
-		Silent:      flags.Silent,
-		AssumeYes:   flags.AssumeYes,
-		Dry:         flags.Dry || flags.Status,
-		Summary:     flags.Summary,
-		Parallel:    flags.Parallel,
-		Color:       flags.Color,
-		Concurrency: flags.Concurrency,
-		Interval:    flags.Interval,
-
-		Stdin:  os.Stdin,
-		Stdout: os.Stdout,
-		Stderr: os.Stderr,
-
-		OutputStyle: flags.Output,
-		TaskSorter:  taskSorter,
-	}
-
-	listOptions := task.NewListOptions(flags.List, flags.ListAll, flags.ListJson, flags.NoStatus)
-	if err := listOptions.Validate(); err != nil {
-		return err
+		fmt.Println(script)
+		return nil
 	}
 
+	e := task.NewExecutor(
+		flags.WithFlags(),
+		task.WithVersionCheck(true),
+	)
 	if err := e.Setup(); err != nil {
 		return err
 	}
 
-	// If the download flag is specified, we should stop execution as soon as
-	// taskfile is downloaded
-	if flags.Download {
-		return nil
-	}
-
-	if (listOptions.ShouldListTasks()) && flags.Silent {
-		return e.ListTaskNames(flags.ListAll)
+	if flags.ClearCache {
+		cachePath := filepath.Join(e.TempDir.Remote, "remote")
+		return os.RemoveAll(cachePath)
 	}
 
+	listOptions := task.NewListOptions(
+		flags.List,
+		flags.ListAll,
+		flags.ListJson,
+		flags.NoStatus,
+	)
 	if listOptions.ShouldListTasks() {
+		if flags.Silent {
+			return e.ListTaskNames(flags.ListAll)
+		}
 		foundTasks, err := e.ListTasks(listOptions)
 		if err != nil {
 			return err
@@ -165,26 +143,29 @@ func run() error {
 		return nil
 	}
 
-	var (
-		calls   []*ast.Call
-		globals *ast.Vars
-	)
-
-	tasksAndVars, cliArgs, err := getArgs()
+	// Parse the remaining arguments
+	cliArgsPreDash, cliArgsPostDash, err := args.Get()
 	if err != nil {
 		return err
 	}
-
-	calls, globals = args.Parse(tasksAndVars...)
+	calls, globals := args.Parse(cliArgsPreDash...)
 
 	// If there are no calls, run the default task instead
 	if len(calls) == 0 {
-		calls = append(calls, &ast.Call{Task: "default"})
+		calls = append(calls, &task.Call{Task: "default"})
 	}
 
-	globals.Set("CLI_ARGS", ast.Var{Value: cliArgs})
+	cliArgsPostDashQuoted, err := args.ToQuotedString(cliArgsPostDash)
+	if err != nil {
+		return err
+	}
+	globals.Set("CLI_ARGS", ast.Var{Value: cliArgsPostDashQuoted})
+	globals.Set("CLI_ARGS_LIST", ast.Var{Value: cliArgsPostDash})
 	globals.Set("CLI_FORCE", ast.Var{Value: flags.Force || flags.ForceAll})
-	e.Taskfile.Vars.Merge(globals)
+	globals.Set("CLI_SILENT", ast.Var{Value: flags.Silent})
+	globals.Set("CLI_VERBOSE", ast.Var{Value: flags.Verbose})
+	globals.Set("CLI_OFFLINE", ast.Var{Value: flags.Offline})
+	e.Taskfile.Vars.Merge(globals, nil)
 
 	if !flags.Watch {
 		e.InterceptInterruptSignals()
@@ -198,24 +179,3 @@ func run() error {
 
 	return e.Run(ctx, calls...)
 }
-
-func getArgs() ([]string, string, error) {
-	var (
-		args          = pflag.Args()
-		doubleDashPos = pflag.CommandLine.ArgsLenAtDash()
-	)
-
-	if doubleDashPos == -1 {
-		return args, "", nil
-	}
-
-	var quotedCliArgs []string
-	for _, arg := range args[doubleDashPos:] {
-		quotedCliArg, err := syntax.Quote(arg, syntax.LangBash)
-		if err != nil {
-			return nil, "", err
-		}
-		quotedCliArgs = append(quotedCliArgs, quotedCliArg)
-	}
-	return args[:doubleDashPos], strings.Join(quotedCliArgs, " "), nil
-}

cmd/tmp/main.go

@@ -0,0 +1,38 @@
+package main
+
+import (
+	"context"
+	"fmt"
+	"net/http"
+	"time"
+)
+
+func main() {
+	ctx, cancel := context.WithTimeout(context.Background(), time.Millisecond)
+	defer cancel()
+	if err := run(ctx); err != nil {
+		fmt.Println(ctx.Err())
+		fmt.Println(err)
+	}
+}
+
+func run(ctx context.Context) error {
+	req, err := http.NewRequest("GET", "https://taskfile.dev/schema.json", nil)
+	if err != nil {
+		fmt.Println(1)
+		return err
+	}
+
+	resp, err := http.DefaultClient.Do(req.WithContext(ctx))
+	if err != nil {
+		if ctx.Err() != nil {
+			fmt.Println(2)
+			return err
+		}
+		fmt.Println(3)
+		return err
+	}
+	defer resp.Body.Close()
+
+	return nil
+}

compiler.go

@@ -1,16 +1,15 @@
-package compiler
+package task
 
 import (
 	"bytes"
 	"context"
-	"encoding/json"
 	"fmt"
+	"os"
 	"path/filepath"
 	"strings"
 	"sync"
 
-	"gopkg.in/yaml.v3"
-
+	"github.com/go-task/task/v3/internal/env"
 	"github.com/go-task/task/v3/internal/execext"
 	"github.com/go-task/task/v3/internal/filepathext"
 	"github.com/go-task/task/v3/internal/logger"
@@ -37,46 +36,29 @@ func (c *Compiler) GetTaskfileVariables() (*ast.Vars, error) {
 	return c.getVariables(nil, nil, true)
 }
 
-func (c *Compiler) GetVariables(t *ast.Task, call *ast.Call) (*ast.Vars, error) {
+func (c *Compiler) GetVariables(t *ast.Task, call *Call) (*ast.Vars, error) {
 	return c.getVariables(t, call, true)
 }
 
-func (c *Compiler) FastGetVariables(t *ast.Task, call *ast.Call) (*ast.Vars, error) {
+func (c *Compiler) FastGetVariables(t *ast.Task, call *Call) (*ast.Vars, error) {
 	return c.getVariables(t, call, false)
 }
 
-func (c *Compiler) getVariables(t *ast.Task, call *ast.Call, evaluateShVars bool) (*ast.Vars, error) {
-	result := GetEnviron()
-	if t != nil {
-		specialVars, err := c.getSpecialVars(t)
-		if err != nil {
-			return nil, err
-		}
-		for k, v := range specialVars {
-			result.Set(k, ast.Var{Value: v})
-		}
+func (c *Compiler) getVariables(t *ast.Task, call *Call, evaluateShVars bool) (*ast.Vars, error) {
+	result := env.GetEnviron()
+	specialVars, err := c.getSpecialVars(t, call)
+	if err != nil {
+		return nil, err
+	}
+	for k, v := range specialVars {
+		result.Set(k, ast.Var{Value: v})
 	}
 
 	getRangeFunc := func(dir string) func(k string, v ast.Var) error {
 		return func(k string, v ast.Var) error {
-			tr := templater.Templater{Vars: result}
+			cache := &templater.Cache{Vars: result}
 			// Replace values
-			newVar := ast.Var{}
-			switch value := v.Value.(type) {
-			case string:
-				newVar.Value = tr.Replace(value)
-			default:
-				newVar.Value = value
-			}
-			newVar.Sh = tr.Replace(v.Sh)
-			newVar.Ref = v.Ref
-			newVar.Json = tr.Replace(v.Json)
-			newVar.Yaml = tr.Replace(v.Yaml)
-			newVar.Dir = v.Dir
-			// If the variable is a reference, we can resolve it
-			if newVar.Ref != "" {
-				newVar.Value = result.Get(newVar.Ref).Value
-			}
+			newVar := templater.ReplaceVar(v, cache)
 			// If the variable should not be evaluated, but is nil, set it to an empty string
 			// This stops empty interface errors when using the templater to replace values later
 			if !evaluateShVars && newVar.Value == nil {
@@ -89,28 +71,16 @@ func (c *Compiler) getVariables(t *ast.Task, call *ast.Call, evaluateShVars bool
 				return nil
 			}
 			// Now we can check for errors since we've handled all the cases when we don't want to evaluate
-			if err := tr.Err(); err != nil {
+			if err := cache.Err(); err != nil {
 				return err
 			}
-			// Evaluate JSON
-			if newVar.Json != "" {
-				if err := json.Unmarshal([]byte(newVar.Json), &newVar.Value); err != nil {
-					return err
-				}
-			}
-			// Evaluate YAML
-			if newVar.Yaml != "" {
-				if err := yaml.Unmarshal([]byte(newVar.Yaml), &newVar.Value); err != nil {
-					return err
-				}
-			}
-			// If the variable is not dynamic, we can set it and return
-			if newVar.Value != nil || newVar.Sh == "" {
+			// If the variable is already set, we can set it and return
+			if newVar.Value != nil || newVar.Sh == nil {
 				result.Set(k, ast.Var{Value: newVar.Value})
 				return nil
 			}
 			// If the variable is dynamic, we need to resolve it first
-			static, err := c.HandleDynamicVar(newVar, dir)
+			static, err := c.HandleDynamicVar(newVar, dir, env.GetFromVars(result))
 			if err != nil {
 				return err
 			}
@@ -124,52 +94,69 @@ func (c *Compiler) getVariables(t *ast.Task, call *ast.Call, evaluateShVars bool
 	if t != nil {
 		// NOTE(@andreynering): We're manually joining these paths here because
 		// this is the raw task, not the compiled one.
-		tr := templater.Templater{Vars: result}
-		dir := tr.Replace(t.Dir)
-		if err := tr.Err(); err != nil {
+		cache := &templater.Cache{Vars: result}
+		dir := templater.Replace(t.Dir, cache)
+		if err := cache.Err(); err != nil {
 			return nil, err
 		}
 		dir = filepathext.SmartJoin(c.Dir, dir)
 		taskRangeFunc = getRangeFunc(dir)
 	}
 
-	if err := c.TaskfileEnv.Range(rangeFunc); err != nil {
-		return nil, err
-	}
-	if err := c.TaskfileVars.Range(rangeFunc); err != nil {
-		return nil, err
-	}
-	if t != nil {
-		if err := t.IncludedTaskfileVars.Range(taskRangeFunc); err != nil {
+	for k, v := range c.TaskfileEnv.All() {
+		if err := rangeFunc(k, v); err != nil {
 			return nil, err
 		}
-		if err := t.IncludeVars.Range(rangeFunc); err != nil {
+	}
+	for k, v := range c.TaskfileVars.All() {
+		if err := rangeFunc(k, v); err != nil {
 			return nil, err
 		}
 	}
+	if t != nil {
+		for k, v := range t.IncludeVars.All() {
+			if err := rangeFunc(k, v); err != nil {
+				return nil, err
+			}
+		}
+		for k, v := range t.IncludedTaskfileVars.All() {
+			if err := taskRangeFunc(k, v); err != nil {
+				return nil, err
+			}
+		}
+	}
 
 	if t == nil || call == nil {
 		return result, nil
 	}
 
-	if err := call.Vars.Range(rangeFunc); err != nil {
-		return nil, err
+	for k, v := range call.Vars.All() {
+		if err := rangeFunc(k, v); err != nil {
+			return nil, err
+		}
 	}
-	if err := t.Vars.Range(taskRangeFunc); err != nil {
-		return nil, err
+	for k, v := range t.Vars.All() {
+		if err := taskRangeFunc(k, v); err != nil {
+			return nil, err
+		}
 	}
 
 	return result, nil
 }
 
-func (c *Compiler) HandleDynamicVar(v ast.Var, dir string) (string, error) {
+func (c *Compiler) HandleDynamicVar(v ast.Var, dir string, e []string) (string, error) {
 	c.muDynamicCache.Lock()
 	defer c.muDynamicCache.Unlock()
 
+	// If the variable is not dynamic or it is empty, return an empty string
+	if v.Sh == nil || *v.Sh == "" {
+		return "", nil
+	}
+
 	if c.dynamicCache == nil {
 		c.dynamicCache = make(map[string]string, 30)
 	}
-	if result, ok := c.dynamicCache[v.Sh]; ok {
+	if result, ok := c.dynamicCache[*v.Sh]; ok {
 		return result, nil
 	}
 
@@ -180,10 +167,11 @@ func (c *Compiler) HandleDynamicVar(v ast.Var, dir string) (string, error) {
 
 	var stdout bytes.Buffer
 	opts := &execext.RunCommandOptions{
-		Command: v.Sh,
+		Command: *v.Sh,
 		Dir:     dir,
 		Stdout:  &stdout,
 		Stderr:  c.Logger.Stderr,
+		Env:     e,
 	}
 	if err := execext.RunCommand(context.Background(), opts); err != nil {
 		return "", fmt.Errorf(`task: Command "%s" failed: %s`, opts.Command, err)
@@ -194,13 +182,13 @@ func (c *Compiler) HandleDynamicVar(v ast.Var, dir string) (string, error) {
 	result := strings.TrimSuffix(stdout.String(), "\r\n")
 	result = strings.TrimSuffix(result, "\n")
 
-	c.dynamicCache[v.Sh] = result
-	c.Logger.VerboseErrf(logger.Magenta, "task: dynamic variable: %q result: %q\n", v.Sh, result)
+	c.dynamicCache[*v.Sh] = result
+	c.Logger.VerboseErrf(logger.Magenta, "task: dynamic variable: %q result: %q\n", *v.Sh, result)
 
 	return result, nil
 }
 
-// ResetCache clear the dymanic variables cache
+// ResetCache clear the dynamic variables cache
 func (c *Compiler) ResetCache() {
 	c.muDynamicCache.Lock()
 	defer c.muDynamicCache.Unlock()
@@ -208,14 +196,30 @@ func (c *Compiler) ResetCache() {
 	c.dynamicCache = nil
 }
 
-func (c *Compiler) getSpecialVars(t *ast.Task) (map[string]string, error) {
-	return map[string]string{
-		"TASK":             t.Task,
+func (c *Compiler) getSpecialVars(t *ast.Task, call *Call) (map[string]string, error) {
+	allVars := map[string]string{
+		"TASK_EXE":         filepath.ToSlash(os.Args[0]),
 		"ROOT_TASKFILE":    filepathext.SmartJoin(c.Dir, c.Entrypoint),
 		"ROOT_DIR":         c.Dir,
-		"TASKFILE":         t.Location.Taskfile,
-		"TASKFILE_DIR":     filepath.Dir(t.Location.Taskfile),
 		"USER_WORKING_DIR": c.UserWorkingDir,
 		"TASK_VERSION":     version.GetVersion(),
-	}, nil
+	}
+	if t != nil {
+		allVars["TASK"] = t.Task
+		allVars["TASK_DIR"] = filepathext.SmartJoin(c.Dir, t.Dir)
+		allVars["TASKFILE"] = t.Location.Taskfile
+		allVars["TASKFILE_DIR"] = filepath.Dir(t.Location.Taskfile)
+	} else {
+		allVars["TASK"] = ""
+		allVars["TASK_DIR"] = ""
+		allVars["TASKFILE"] = ""
+		allVars["TASKFILE_DIR"] = ""
+	}
+	if call != nil {
+		allVars["ALIAS"] = call.Task
+	} else {
+		allVars["ALIAS"] = ""
+	}
+
+	return allVars, nil
 }

completion.go

@@ -0,0 +1,34 @@
+package task
+
+import (
+	_ "embed"
+	"fmt"
+)
+
+//go:embed completion/bash/task.bash
+var completionBash string
+
+//go:embed completion/fish/task.fish
+var completionFish string
+
+//go:embed completion/ps/task.ps1
+var completionPowershell string
+
+//go:embed completion/zsh/_task
+var completionZsh string
+
+func Completion(completion string) (string, error) {
+	// Get the file extension for the selected shell
+	switch completion {
+	case "bash":
+		return completionBash, nil
+	case "fish":
+		return completionFish, nil
+	case "powershell":
+		return completionPowershell, nil
+	case "zsh":
+		return completionZsh, nil
+	default:
+		return "", fmt.Errorf("unknown shell: %s", completion)
+	}
+}

completion/fish/task.fish

@@ -1,8 +1,25 @@
-set GO_TASK_PROGNAME task
+set -l GO_TASK_PROGNAME task
+
+function __task_get_tasks --description "Prints all available tasks with their description" --inherit-variable GO_TASK_PROGNAME
+  # Check if the global task is requested
+  set -l global_task false
+  commandline --current-process | read --tokenize --list --local cmd_args
+  for arg in $cmd_args
+    if test "_$arg" = "_--"
+      break # ignore arguments to be passed to the task
+    end
+    if test "_$arg" = "_--global" -o "_$arg" = "_-g"
+      set global_task true
+      break
+    end
+  end
 
-function __task_get_tasks --description "Prints all available tasks with their description"
   # Read the list of tasks (and potential errors)
-  $GO_TASK_PROGNAME --list-all 2>&1 | read -lz rawOutput
+  if $global_task
+    $GO_TASK_PROGNAME --global --list-all
+  else
+    $GO_TASK_PROGNAME --list-all
+  end 2>&1 | read -lz rawOutput
 
   # Return on non-zero exit code (for cases when there is no Taskfile found or etc.)
   if test $status -ne 0
@@ -10,7 +27,7 @@ function __task_get_tasks --description "Prints all available tasks with their d
   end
 
   # Grab names and descriptions (if any) of the tasks
-  set -l output (echo $rawOutput | sed -e '1d; s/\* \(.*\):\s*\(.*\)\s*(aliases.*/\1\t\2/' -e 's/\* \(.*\):\s*\(.*\)/\1\t\2/'| string split0)
+  set -l output (echo $rawOutput | sed -e '1d; s/\* \(.*\):\s*\(.*\)\s*(\(aliases.*\))/\1\t\2\t\3/' -e 's/\* \(.*\):\s*\(.*\)/\1\t\2/'| string split0)
   if test $output
     echo $output
   end

completion/zsh/_task

@@ -1,6 +1,5 @@
 #compdef task
-
-local context state state_descr line
+compdef _task task
 typeset -A opt_args
 
 _GO_TASK_COMPLETION_LIST_OPTION="${GO_TASK_COMPLETION_LIST_OPTION:---list-all}"
@@ -12,7 +11,9 @@ function __task_list() {
     local taskfile item task desc
 
     cmd=(task)
-    taskfile="${(v)opt_args[(i)-t|--taskfile]}"
+    taskfile=${(Qv)opt_args[(i)-t|--taskfile]}
+    taskfile=${taskfile//\~/$HOME}
+
 
     if [[ -n "$taskfile" && -f "$taskfile" ]]; then
         enabled=1
@@ -37,26 +38,33 @@ function __task_list() {
     _describe 'Task to run' scripts
 }
 
-_arguments \
-    '(-C --concurrency)'{-C,--concurrency}'[limit number of concurrent tasks]: ' \
-    '(-p --parallel)'{-p,--parallel}'[run command-line tasks in parallel]' \
-    '(-f --force)'{-f,--force}'[run even if task is up-to-date]' \
-    '(-c --color)'{-c,--color}'[colored output]' \
-    '(-d --dir)'{-d,--dir}'[dir to run in]:execution dir:_dirs' \
-    '(--dry)--dry[dry-run mode, compile and print tasks only]' \
-    '(-o --output)'{-o,--output}'[set output style]:style:(interleaved group prefixed)' \
-    '(--output-group-begin)--output-group-begin[message template before grouped output]:template text: ' \
-    '(--output-group-end)--output-group-end[message template after grouped output]:template text: ' \
-    '(-s --silent)'{-s,--silent}'[disable echoing]' \
-    '(--status)--status[exit non-zero if supplied tasks not up-to-date]' \
-    '(--summary)--summary[show summary\: field from tasks instead of running them]' \
-    '(-t --taskfile)'{-t,--taskfile}'[specify a different taskfile]:taskfile:_files' \
-    '(-v --verbose)'{-v,--verbose}'[verbose mode]' \
-    '(-w --watch)'{-w,--watch}'[watch-mode for given tasks, re-run when inputs change]' \
-    + '(operation)' \
-        {-l,--list}'[list describable tasks]' \
-        {-a,--list-all}'[list all tasks]' \
-        {-i,--init}'[create new Taskfile.yml]' \
-        '(-*)'{-h,--help}'[show help]' \
-        '(-*)--version[show version and exit]' \
-        '*: :__task_list'
+_task() {
+    _arguments \
+        '(-C --concurrency)'{-C,--concurrency}'[limit number of concurrent tasks]: ' \
+        '(-p --parallel)'{-p,--parallel}'[run command-line tasks in parallel]' \
+        '(-f --force)'{-f,--force}'[run even if task is up-to-date]' \
+        '(-c --color)'{-c,--color}'[colored output]' \
+        '(-d --dir)'{-d,--dir}'[dir to run in]:execution dir:_dirs' \
+        '(--dry)--dry[dry-run mode, compile and print tasks only]' \
+        '(-o --output)'{-o,--output}'[set output style]:style:(interleaved group prefixed)' \
+        '(--output-group-begin)--output-group-begin[message template before grouped output]:template text: ' \
+        '(--output-group-end)--output-group-end[message template after grouped output]:template text: ' \
+        '(-s --silent)'{-s,--silent}'[disable echoing]' \
+        '(--status)--status[exit non-zero if supplied tasks not up-to-date]' \
+        '(--summary)--summary[show summary\: field from tasks instead of running them]' \
+        '(-t --taskfile)'{-t,--taskfile}'[specify a different taskfile]:taskfile:_files' \
+        '(-v --verbose)'{-v,--verbose}'[verbose mode]' \
+        '(-w --watch)'{-w,--watch}'[watch-mode for given tasks, re-run when inputs change]' \
+        + '(operation)' \
+            {-l,--list}'[list describable tasks]' \
+            {-a,--list-all}'[list all tasks]' \
+            {-i,--init}'[create new Taskfile.yml]' \
+            '(-*)'{-h,--help}'[show help]' \
+            '(-*)--version[show version and exit]' \
+            '*: :__task_list'
+}
+
+# don't run the completion function when being source-ed or eval-ed
+if [ "$funcstack[1]" = "_task" ]; then
+    _task "$@"
+fi

docs/crowdin.yml

@@ -1,15 +0,0 @@
-project_id: "574591"
-api_token_env: CROWDIN_PERSONAL_TOKEN
-preserve_hierarchy: true
-
-files:
-  - source: /docs/**/*
-    translation: /i18n/%locale%/docusaurus-plugin-content-docs/current/**/%original_file_name%
-    ignore:
-      - /**/*.json
-
-  - source: /blog/**/*
-    translation: /i18n/%locale%/docusaurus-plugin-content-blog/**/%original_file_name%
-
-  - source: /i18n/en/**/*.json
-    translation: /i18n/%locale%/**/%original_file_name%

docs/docs/experiments/any_variables.mdx

@@ -1,346 +0,0 @@
----
-slug: /experiments/any-variables/
----
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-# Any Variables (#1415)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any
-time_. We strongly recommend that you do not use these features in a production
-environment. They are intended for testing and feedback only.
-
-:::
-
-Currently, Task only supports string variables. This experiment allows you to
-specify and use the following variable types:
-
-- `string`
-- `bool`
-- `int`
-- `float`
-- `array`
-- `map`
-
-This allows you to have a lot more flexibility in how you use variables in
-Task's templating engine. There are two active proposals for this experiment.
-Click on the tabs below to switch between them.
-
-<Tabs defaultValue="1" queryString="proposal"
-  values={[
-    {label: 'Proposal 1', value: '1'},
-    {label: 'Proposal 2', value: '2'}
-  ]}>
-
-<TabItem value="1">
-
-:::warning
-
-This experiment proposal breaks the following functionality:
-
-- Dynamically defined variables (using the `sh` keyword)
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable:
-`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
-][enabling-experiments] for more information.
-
-:::
-
-## Maps
-
-This proposal removes support for the `sh` keyword in favour of a new syntax for
-dynamically defined variables, This allows you to define a map directly as you
-would for any other type:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO: {a: 1, b: 2, c: 3} # <-- Directly defined map on the `FOO` key
-    cmds:
-      - 'echo {{.FOO.a}}'
-```
-
-## Migration
-
-Taskfiles with dynamically defined variables via the `sh` subkey will no longer
-work with this experiment enabled. In order to keep using dynamically defined
-variables, you will need to migrate your Taskfile to use the new syntax.
-
-Previously, you might have defined a dynamic variable like this:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      CALCULATED_VAR:
-        sh: 'echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-With this experiment enabled, you will need to remove the `sh` subkey and define
-your command as a string that begins with a `$`. This will instruct Task to
-interpret the string as a command instead of a literal value and the variable
-will be populated with the output of the command. For example:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      CALCULATED_VAR: '$echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-If your current Taskfile contains a string variable that begins with a `$`, you
-will now need to escape the `$` with a backslash (`\`) to stop Task from
-executing it as a command.
-
-</TabItem>
-
-<TabItem value="2">
-
-:::info
-
-To enable this experiment, set the environment variable:
-`TASK_X_ANY_VARIABLES=2`. Check out [our guide to enabling experiments
-][enabling-experiments] for more information.
-
-:::
-
-## Maps
-
-This proposal maintains backwards-compatibility and the `sh` subkey and adds
-another new `map` subkey for defining map variables:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO:
-        map: {a: 1, b: 2, c: 3} # <-- Defined using the `map' subkey instead of directly on 'FOO'
-      BAR: true # <-- Other types of variables are still defined directly on the key
-      BAZ:
-        sh: 'echo Hello Task' # <-- The `sh` subkey is still supported
-    cmds:
-      - 'echo {{.FOO.a}}'
-```
-
-## Parsing JSON and YAML
-
-In addition to the new `map` keyword, this proposal also adds support for the
-`json` and `yaml` keywords for parsing JSON and YAML strings into real
-objects/arrays. This is similar to the `fromJSON` template function, but means
-that you only have to parse the JSON/YAML once when you declare the variable,
-instead of every time you want to access a value.
-
-Before:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO: '{"a": 1, "b": 2, "c": 3}' # <-- JSON string
-    cmds:
-      - 'echo {{(fromJSON .FOO).a}}' # <-- Parse JSON string every time you want to access a value
-      - 'echo {{(fromJSON .FOO).b}}'
-```
-
-After:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO:
-        json: '{"a": 1, "b": 2, "c": 3}' # <-- JSON string parsed once
-    cmds:
-      - 'echo {{.FOO.a}}' # <-- Access values directly
-      - 'echo {{.FOO.b}}'
-```
-
-## Variables by reference
-
-Lastly, this proposal adds support for defining and passing variables by
-reference. This is really important now that variables can be types other than a
-string. Previously, to send a variable from one task to another, you would have
-to use the templating system to pass it:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO: [A, B, C] # <-- FOO is defined as an array
-    cmds:
-      - task: bar
-        vars:
-          FOO: '{{.FOO}}' # <-- FOO gets converted to a string when passed to bar
-  bar:
-    cmds:
-      - 'echo {{index .FOO 0}}' # <-- FOO is a string so the task outputs '91' which is the ASCII code for '[' instead of the expected 'A'
-```
-
-Unfortunately, this results in the value always being passed as a string as this
-is the output type of the templater and operations on the passed variable may
-not behave as expected. With this proposal, you can now pass variables by
-reference using the `ref` subkey:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO: [A, B, C] # <-- FOO is defined as an array
-    cmds:
-      - task: bar
-        vars:
-          FOO:
-            ref: FOO # <-- FOO gets passed by reference to bar and maintains its type
-  bar:
-    cmds:
-      - 'echo {{index .FOO 0}}' # <-- FOO is still a map so the task outputs 'A' as expected
-```
-
-This means that the type of the variable is maintained when it is passed to
-another Task. This also works the same way when calling `deps` and when defining
-a variable and can be used in any combination:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      FOO: [A, B, C] # <-- FOO is defined as an array
-      BAR:
-        ref: FOO # <-- BAR is defined as a reference to FOO
-    deps:
-      - task: bar
-        vars:
-          BAR:
-            ref: BAR # <-- BAR gets passed by reference to bar and maintains its type
-  bar:
-    cmds:
-      - 'echo {{index .BAR 0}}' # <-- BAR still refers to FOO so the task outputs 'A'
-```
-
-</TabItem></Tabs>
-
----
-
-## Common to both proposals
-
-Both proposals add support for all other variable types by directly defining
-them in the Taskfile. For example:
-
-### Evaluating booleans
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      BOOL: false
-    cmds:
-      - '{{if .BOOL}}echo foo{{end}}'
-```
-
-### Arithmetic
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      INT: 10
-      FLOAT: 3.14159
-    cmds:
-      - 'echo {{add .INT .FLOAT}}'
-```
-
-### Ranging
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      ARRAY: [1, 2, 3]
-    cmds:
-      - 'echo {{range .ARRAY}}{{.}}{{end}}'
-```
-
-There are many more templating functions which can be used with the new types of
-variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
-
-## Looping over variables
-
-Previously, you would have to use a delimiter separated string to loop over an
-arbitrary list of items in a variable and split them by using the `split` subkey
-to specify the delimiter:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: 'foo,bar,baz'
-    cmds:
-      - for:
-          var: LIST
-          split: ','
-        cmd: echo {{.ITEM}}
-```
-
-Both of these proposals add support for looping over "collection-type" variables
-using the `for` keyword, so now you are able to loop over a map/array variable
-directly:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: [foo, bar, baz]
-    cmds:
-      - for:
-          var: LIST
-        cmd: echo {{.ITEM}}
-```
-
-When looping over a map we also make an additional `{{.KEY}}` variable availabe
-that holds the string value of the map key. Remember that maps are unordered, so
-the order in which the items are looped over is random.
-
-<!-- prettier-ignore-start -->
-[enabling-experiments]: /experiments/#enabling-experiments
-[slim-sprig]: https://go-task.github.io/slim-sprig/
-<!-- prettier-ignore-end -->

docs/docs/experiments/remote_taskfiles.md

@@ -1,105 +0,0 @@
----
-slug: /experiments/remote-taskfiles/
----
-
-# Remote Taskfiles (#1317)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any
-time_. We strongly recommend that you do not use these features in a production
-environment. They are intended for testing and feedback only.
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable:
-`TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments
-][enabling-experiments] for more information.
-
-:::
-
-This experiment allows you to specify a remote Taskfile URL when including a
-Taskfile. For example:
-
-```yaml
-version: '3'
-
-includes:
-  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
-```
-
-This works exactly the same way that including a local file does. Any tasks in
-the remote Taskfile will be available to run from your main Taskfile via the
-namespace `my-remote-namespace`. For example, if the remote file contains the
-following:
-
-```yaml
-version: '3'
-
-tasks:
-  hello:
-    silent: true
-    cmds:
-      - echo "Hello from the remote Taskfile!"
-```
-
-and you run `task my-remote-namespace:hello`, it will print the text: "Hello
-from the remote Taskfile!" to your console.
-
-## Security
-
-Running commands from sources that you do not control is always a potential
-security risk. For this reason, we have added some checks when using remote
-Taskfiles:
-
-1. When running a task from a remote Taskfile for the first time, Task will
-   print a warning to the console asking you to check that you are sure that you
-   trust the source of the Taskfile. If you do not accept the prompt, then Task
-   will exit with code `104` (not trusted) and nothing will run. If you accept
-   the prompt, the remote Taskfile will run and further calls to the remote
-   Taskfile will not prompt you again.
-2. Whenever you run a remote Taskfile, Task will create and store a checksum of
-   the file that you are running. If the checksum changes, then Task will print
-   another warning to the console to inform you that the contents of the remote
-   file has changed. If you do not accept the prompt, then Task will exit with
-   code `104` (not trusted) and nothing will run. If you accept the prompt, the
-   checksum will be updated and the remote Taskfile will run.
-
-Sometimes you need to run Task in an environment that does not have an
-interactive terminal, so you are not able to accept a prompt. In these cases you
-are able to tell task to accept these prompts automatically by using the `--yes`
-flag. Before enabling this flag, you should:
-
-1. Be sure that you trust the source and contents of the remote Taskfile.
-2. Consider using a pinned version of the remote Taskfile (e.g. A link
-   containing a commit hash) to prevent Task from automatically accepting a
-   prompt that says a remote Taskfile has changed.
-
-Task currently supports both `http` and `https` URLs. However, the `http`
-requests will not execute by default unless you run the task with the
-`--insecure` flag. This is to protect you from accidentally running a remote
-Taskfile that is hosted on and unencrypted connection. Sources that are not
-protected by TLS are vulnerable to [man-in-the-middle
-attacks][man-in-the-middle-attacks] and should be avoided unless you know what
-you are doing.
-
-## Caching & Running Offline
-
-Whenever you run a remote Taskfile, the latest copy will be downloaded from the
-internet and cached locally. If for whatever reason, you lose access to the
-internet, you will still be able to run your tasks by specifying the `--offline`
-flag. This will tell Task to use the latest cached version of the file instead
-of trying to download it. You are able to use the `--download` flag to update
-the cached version of the remote files without running any tasks.
-
-By default, Task will timeout requests to download remote files after 10 seconds
-and look for a cached copy instead. This timeout can be configured by setting
-the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will
-set the timeout to 5 seconds.
-
-<!-- prettier-ignore-start -->
-[enabling-experiments]: /experiments/#enabling-experiments
-[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack
-<!-- prettier-ignore-end -->

docs/docs/installation.md

@@ -1,303 +0,0 @@
----
-slug: /installation/
-sidebar_position: 2
----
-
-# Installation
-
-Task offers many installation methods. Check out the available methods below.
-
-## Package Managers
-
-### Homebrew
-
-If you're on macOS or Linux and have [Homebrew][homebrew] installed, getting
-Task is as simple as running:
-
-```shell
-brew install go-task/tap/go-task
-```
-
-The above Formula is
-[maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb).
-
-Recently, Task was also made available
-[on the official Homebrew repository](https://formulae.brew.sh/formula/go-task),
-so you also have that option if you prefer:
-
-```shell
-brew install go-task
-```
-
-### Tea
-
-If you're on macOS or Linux and have [tea][tea] installed, getting Task is as
-simple as running:
-
-```shell
-tea task
-```
-
-or, if you have tea’s magic enabled:
-
-```shell
-task
-```
-
-This installation method is community owned. After a new release of Task, they
-are automatically released by tea in a minimum of time.
-
-### Snap
-
-Task is available in [Snapcraft][snapcraft], but keep in mind that your Linux
-distribution should allow classic confinement for Snaps to Task work right:
-
-```shell
-sudo snap install task --classic
-```
-
-### Chocolatey
-
-If you're on Windows and have [Chocolatey][choco] installed, getting Task is as
-simple as running:
-
-```shell
-choco install go-task
-```
-
-This installation method is community owned.
-
-### Scoop
-
-If you're on Windows and have [Scoop][scoop] installed, getting Task is as
-simple as running:
-
-```shell
-scoop install task
-```
-
-This installation method is community owned. After a new release of Task, it may
-take some time until it's available on Scoop.
-
-### AUR
-
-If you're on Arch Linux you can install Task from
-[AUR](https://aur.archlinux.org/packages/go-task-bin) using your favorite
-package manager such as `yay`, `pacaur` or `yaourt`:
-
-```shell
-yay -S go-task-bin
-```
-
-Alternatively, there's
-[this package](https://aur.archlinux.org/packages/go-task) which installs from
-the source code instead of downloading the binary from the
-[releases page](https://github.com/go-task/task/releases):
-
-```shell
-yay -S go-task
-```
-
-This installation method is community owned.
-
-### Fedora
-
-If you're on Fedora Linux you can install Task from the official
-[Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
-repository using `dnf`:
-
-```shell
-sudo dnf install go-task
-```
-
-This installation method is community owned. After a new release of Task, it may
-take some time until it's available in
-[Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/).
-
-### Nix
-
-If you're on NixOS or have Nix installed you can install Task from
-[nixpkgs](https://github.com/NixOS/nixpkgs):
-
-```shell
-nix-env -iA nixpkgs.go-task
-```
-
-This installation method is community owned. After a new release of Task, it may
-take some time until it's available in
-[nixpkgs](https://github.com/NixOS/nixpkgs).
-
-### npm
-
-You can also use Node and npm to install Task by installing
-[this package](https://www.npmjs.com/package/@go-task/cli).
-
-```shell
-npm install -g @go-task/cli
-```
-
-### Winget
-
-If you are using Windows and installed the
-[winget](https://github.com/microsoft/winget-cli) package management tool, you
-can install Task from [winget-pkgs](https://github.com/microsoft/winget-pkgs).
-
-```shell
-winget install Task.Task
-```
-
-## Get The Binary
-
-### Binary
-
-You can download the binary from the [releases page on GitHub][releases] and add
-to your `$PATH`.
-
-DEB and RPM packages are also available.
-
-The `task_checksums.txt` file contains the SHA-256 checksum for each file.
-
-### Install Script
-
-We also have an [install script][installscript] which is very useful in
-scenarios like CI. Many thanks to [GoDownloader][godownloader] for enabling the
-easy generation of this script.
-
-By default, it installs on the `./bin` directory relative to the working
-directory:
-
-```shell
-sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d
-```
-
-It is possible to override the installation directory with the `-b` parameter.
-On Linux, common choices are `~/.local/bin` and `~/bin` to install for the
-current user or `/usr/local/bin` to install for all users:
-
-```shell
-sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
-```
-
-:::caution
-
-On macOS and Windows, `~/.local/bin` and `~/bin` are not added to `$PATH` by
-default.
-
-:::
-
-### GitHub Actions
-
-If you want to install Task in GitHub Actions you can try using
-[this action](https://github.com/arduino/setup-task) by the Arduino team:
-
-```yaml
-- name: Install Task
-  uses: arduino/setup-task@v1
-  with:
-    version: 3.x
-    repo-token: ${{ secrets.GITHUB_TOKEN }}
-```
-
-This installation method is community owned.
-
-## Build From Source
-
-### Go Modules
-
-Ensure that you have a supported version of [Go][go] properly installed and
-setup. You can find the minimum required version of Go in the
-[go.mod](https://github.com/go-task/task/blob/main/go.mod#L3) file.
-
-You can then install the latest release globally by running:
-
-```shell
-go install github.com/go-task/task/v3/cmd/task@latest
-```
-
-Or you can install into another directory:
-
-```shell
-env GOBIN=/bin go install github.com/go-task/task/v3/cmd/task@latest
-```
-
-:::tip
-
-For CI environments we recommend using the [install script](#install-script)
-instead, which is faster and more stable, since it'll just download the latest
-released binary.
-
-:::
-
-## Setup completions
-
-Download the autocompletion file corresponding to your shell.
-
-[All completions are available on the Task repository](https://github.com/go-task/task/tree/main/completion).
-
-### Bash
-
-First, ensure that you installed bash-completion using your package manager.
-
-Make the completion file executable:
-
-```shell
-chmod +x path/to/task.bash
-```
-
-After, add this to your `~/.bash_profile`:
-
-```shell
-source path/to/task.bash
-```
-
-### ZSH
-
-Put the `_task` file somewhere in your `$FPATH`:
-
-```shell
-mv path/to/_task /usr/local/share/zsh/site-functions/_task
-```
-
-Ensure that the following is present in your `~/.zshrc`:
-
-```shell
-autoload -U compinit
-compinit -i
-```
-
-ZSH version 5.7 or later is recommended.
-
-### Fish
-
-Move the `task.fish` completion script:
-
-```shell
-mv path/to/task.fish ~/.config/fish/completions/task.fish
-```
-
-### PowerShell
-
-Open your profile script with:
-
-```powershell
-mkdir -Path (Split-Path -Parent $profile) -ErrorAction SilentlyContinue
-notepad $profile
-```
-
-Add the line and save the file:
-
-```shell
-Invoke-Expression -Command path/to/task.ps1
-```
-
-<!-- prettier-ignore-start -->
-[go]: https://golang.org/
-[snapcraft]: https://snapcraft.io/task
-[homebrew]: https://brew.sh/
-[installscript]: https://github.com/go-task/task/blob/main/install-task.sh
-[releases]: https://github.com/go-task/task/releases
-[godownloader]: https://github.com/goreleaser/godownloader
-[choco]: https://chocolatey.org/
-[scoop]: https://scoop.sh/
-[tea]: https://tea.xyz/
-<!-- prettier-ignore-end -->

docs/docs/taskfile_versions.md

@@ -1,263 +0,0 @@
----
-slug: /taskfile-versions/
-sidebar_position: 5
----
-
-# Taskfile Versions
-
-The Taskfile syntax and features changed with time. This document explains what
-changed on each version and how to upgrade your Taskfile.
-
-## What the Taskfile version mean
-
-The Taskfile version follows the Task version. E.g. the change to Taskfile
-version `2` means that Task `v2.0.0` should be release to support it.
-
-The `version:` key on Taskfile accepts a semver string, so either `2`, `2.0` or
-`2.0.0` is accepted. If you choose to use `2.0` Task will not enable future
-`2.1` features, but if you choose to use `2`, then any `2.x.x` features will be
-available, but not `3.0.0+`.
-
-## Version 3 ![latest](https://img.shields.io/badge/latest-brightgreen)
-
-These are some major changes done on `v3`:
-
-- Task's output will now be colored
-- Added support for `.env` like files
-- Added `label:` setting to task so one can override how the task name appear in
-  the logs
-- A global `method:` was added to allow setting the default method, and Task's
-  default changed to `checksum`
-- Two magic variables were added when using `status:`: `CHECKSUM` and
-  `TIMESTAMP` which contains, respectively, the XXH3 checksum and greatest
-  modification timestamp of the files listed on `sources:`
-- Also, the `TASK` variable is always available with the current task name
-- CLI variables are always treated as global variables
-- Added `dir:` option to `includes` to allow choosing on which directory an
-  included Taskfile will run:
-
-```yaml
-includes:
-  docs:
-    taskfile: ./docs
-    dir: ./docs
-```
-
-- Implemented short task syntax. All below syntaxes are equivalent:
-
-```yaml
-version: '3'
-
-tasks:
-  print:
-    cmds:
-      - echo "Hello, World!"
-```
-
-```yaml
-version: '3'
-
-tasks:
-  print:
-    - echo "Hello, World!"
-```
-
-```yaml
-version: '3'
-
-tasks:
-  print: echo "Hello, World!"
-```
-
-- There was a major refactor on how variables are handled. They're now easier to
-  understand. The `expansions:` setting was removed as it became unnecessary.
-  This is the order in which Task will process variables, each level can see the
-  variables set by the previous one and override those.
-  - Environment variables
-  - Global + CLI variables
-  - Call variables
-  - Task variables
-
-## Version 2.6
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of
-Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.6 comes with `preconditions` stanza in tasks.
-
-```yaml
-version: '2'
-
-tasks:
-  upload_environment:
-    preconditions:
-      - test -f .env
-    cmds:
-      - aws s3 cp .env s3://myenvironment
-```
-
-Please check the [documentation][includes]
-
-## Version 2.2
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of
-Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.2 comes with a global `includes` options to include other Taskfiles:
-
-```yaml
-version: '2'
-
-includes:
-  docs: ./documentation # will look for ./documentation/Taskfile.yml
-  docker: ./DockerTasks.yml
-```
-
-## Version 2.1
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of
-Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.1 includes a global `output` option, to allow having more control over
-how commands output are printed to the console (see [documentation][output] for
-more info):
-
-```yaml
-version: '2'
-
-output: prefixed
-
-tasks:
-  server:
-    cmds:
-      - go run main.go
-  prefix: server
-```
-
-From this version it's also possible to ignore errors of a command or task
-(check documentation [here][ignore_errors]):
-
-```yaml
-version: '2'
-
-tasks:
-  example-1:
-    cmds:
-      - cmd: exit 1
-        ignore_error: true
-      - echo "This will be print"
-
-  example-2:
-    cmds:
-      - exit 1
-      - echo "This will be print"
-    ignore_error: true
-```
-
-## Version 2.0
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of
-Task][deprecate-version-2-schema].
-
-:::
-
-At version 2, we introduced the `version:` key, to allow us to evolve Task with
-new features without breaking existing Taskfiles. The new syntax is as follows:
-
-```yaml
-version: '2'
-
-tasks:
-  echo:
-    cmds:
-      - echo "Hello, World!"
-```
-
-Version 2 allows you to write global variables directly in the Taskfile, if you
-don't want to create a `Taskvars.yml`:
-
-```yaml
-version: '2'
-
-vars:
-  GREETING: Hello, World!
-
-tasks:
-  greet:
-    cmds:
-      - echo "{{.GREETING}}"
-```
-
-The variable priority order changed to the following:
-
-1. Task variables
-2. Call variables
-3. Taskfile variables
-4. Taskvars file variables
-5. Environment variables
-
-A new global option was added to configure the number of variables expansions
-(which default to 2):
-
-```yaml
-version: '2'
-
-expansions: 3
-
-vars:
-  FOO: foo
-  BAR: bar
-  BAZ: baz
-  FOOBAR: '{{.FOO}}{{.BAR}}'
-  FOOBARBAZ: '{{.FOOBAR}}{{.BAZ}}'
-
-tasks:
-  default:
-    cmds:
-      - echo "{{.FOOBARBAZ}}"
-```
-
-## Version 1
-
-:::caution
-
-v1 schema support was removed in Task >= v3.0.0.
-
-:::
-
-In the first version of the `Taskfile`, the `version:` key was not available,
-because the tasks was in the root of the YAML document. Like this:
-
-```yaml
-echo:
-  cmds:
-    - echo "Hello, World!"
-```
-
-The variable priority order was also different:
-
-1. Call variables
-2. Environment
-3. Task variables
-4. `Taskvars.yml` variables
-
-<!-- prettier-ignore-start -->
-[deprecate-version-2-schema]: /deprecations/version-2-schema/
-[output]: /usage#output-syntax
-[ignore_errors]: /usage#ignore-errors
-[includes]: /usage#including-other-taskfiles
-<!-- prettier-ignore-end -->

docs/docs/translate.md

@@ -1,22 +0,0 @@
----
-slug: /translate/
-sidebar_position: 12
----
-
-# Translate
-
-Want to help us translate this documentation? In this document we explain how.
-
-Do NOT edit translated markdown files directly on the GitHub repository! We use
-[Crowdin][crowdin] to allow contributors on work on translations. The repository
-is periodically updated with progress from Crowdin.
-
-If you want to have access to the Crowdin project to be able to suggest
-translations, please ask for access on the [#translations channel on our Discord
-server][discord]. If a given language is not being shown to Crowdin yet, just
-ask and we can configure it.
-
-<!-- prettier-ignore-start -->
-[crowdin]: https://crowdin.com/project/taskfile
-[discord]: https://discord.gg/6TY36E39UK
-<!-- prettier-ignore-end -->

docs/i18n/en/code.json

@@ -1,396 +0,0 @@
-{
-  "theme.ErrorPageContent.title": {
-    "message": "This page crashed.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Try again",
-    "description": "The label of the button to try again when the page crashed"
-  },
-  "theme.NotFound.title": {
-    "message": "Page Not Found",
-    "description": "The title of the 404 page"
-  },
-  "theme.NotFound.p1": {
-    "message": "We could not find what you were looking for.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Please contact the owner of the site that linked you to the original URL and let them know their link is broken.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.admonition.note": {
-    "message": "note",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "tip",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.danger": {
-    "message": "danger",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "info",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.caution": {
-    "message": "caution",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Scroll back to top",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archive",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archive",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Blog list page navigation",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Newer Entries",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Older Entries",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Blog post page navigation",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Newer Post",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Older Post",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.blog.post.plurals": {
-    "message": "One post|{count} posts",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} tagged with \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "View All Tags",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Switch between dark and light mode (currently {mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "dark mode",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "light mode",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Home page",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Breadcrumbs",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription": {
-    "message": "{count} items",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Docs pages navigation",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Previous",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Next",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "One doc tagged|{count} docs tagged",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} with \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Version: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "This is unreleased documentation for {siteTitle} {versionLabel} version.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "This is documentation for {siteTitle} {versionLabel}, which is no longer actively maintained.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "For up-to-date documentation, see the {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "latest version",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Edit this page",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Direct link to heading",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " on {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " by {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Last updated{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versions",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Tags:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Close",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Blog recent posts navigation",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copied",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copy code to clipboard",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copy",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Toggle word wrap",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.toggleCollapsedCategoryAriaLabel": {
-    "message": "Toggle the collapsible sidebar category '{label}'",
-    "description": "The ARIA label to toggle the collapsible sidebar category"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Languages",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "On this page",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Read More",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Read more about {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "One min read|{readingTime} min read",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Close navigation bar",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Back to main menu",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Toggle navigation bar",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.SearchBar.seeAll": {
-    "message": "See all {count} results"
-  },
-  "theme.SearchPage.documentsFound.plurals": {
-    "message": "One document found|{count} documents found",
-    "description": "Pluralized label for \"{count} documents found\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.SearchPage.existingResultsTitle": {
-    "message": "Search results for \"{query}\"",
-    "description": "The search page title for non-empty query"
-  },
-  "theme.SearchPage.emptyResultsTitle": {
-    "message": "Search the documentation",
-    "description": "The search page title for empty query"
-  },
-  "theme.SearchPage.inputPlaceholder": {
-    "message": "Type your search here",
-    "description": "The placeholder for search page input"
-  },
-  "theme.SearchPage.inputLabel": {
-    "message": "Search",
-    "description": "The ARIA label for search page input"
-  },
-  "theme.SearchPage.algoliaLabel": {
-    "message": "Search by Algolia",
-    "description": "The ARIA label for Algolia mention"
-  },
-  "theme.SearchPage.noResultsText": {
-    "message": "No results were found",
-    "description": "The paragraph for empty search result"
-  },
-  "theme.SearchPage.fetchingNewResults": {
-    "message": "Fetching new results...",
-    "description": "The paragraph for fetching new search results"
-  },
-  "theme.SearchBar.label": {
-    "message": "Search",
-    "description": "The ARIA label and placeholder for search button"
-  },
-  "theme.SearchModal.searchBox.resetButtonTitle": {
-    "message": "Clear the query",
-    "description": "The label and ARIA label for search box reset button"
-  },
-  "theme.SearchModal.searchBox.cancelButtonText": {
-    "message": "Cancel",
-    "description": "The label and ARIA label for search box cancel button"
-  },
-  "theme.SearchModal.startScreen.recentSearchesTitle": {
-    "message": "Recent",
-    "description": "The title for recent searches"
-  },
-  "theme.SearchModal.startScreen.noRecentSearchesText": {
-    "message": "No recent searches",
-    "description": "The text when no recent searches"
-  },
-  "theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
-    "message": "Save this search",
-    "description": "The label for save recent search button"
-  },
-  "theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
-    "message": "Remove this search from history",
-    "description": "The label for remove recent search button"
-  },
-  "theme.SearchModal.startScreen.favoriteSearchesTitle": {
-    "message": "Favorite",
-    "description": "The title for favorite searches"
-  },
-  "theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
-    "message": "Remove this search from favorites",
-    "description": "The label for remove favorite search button"
-  },
-  "theme.SearchModal.errorScreen.titleText": {
-    "message": "Unable to fetch results",
-    "description": "The title for error screen of search modal"
-  },
-  "theme.SearchModal.errorScreen.helpText": {
-    "message": "You might want to check your network connection.",
-    "description": "The help text for error screen of search modal"
-  },
-  "theme.SearchModal.footer.selectText": {
-    "message": "to select",
-    "description": "The explanatory text of the action for the enter key"
-  },
-  "theme.SearchModal.footer.selectKeyAriaLabel": {
-    "message": "Enter key",
-    "description": "The ARIA label for the Enter key button that makes the selection"
-  },
-  "theme.SearchModal.footer.navigateText": {
-    "message": "to navigate",
-    "description": "The explanatory text of the action for the Arrow up and Arrow down key"
-  },
-  "theme.SearchModal.footer.navigateUpKeyAriaLabel": {
-    "message": "Arrow up",
-    "description": "The ARIA label for the Arrow up key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.navigateDownKeyAriaLabel": {
-    "message": "Arrow down",
-    "description": "The ARIA label for the Arrow down key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.closeText": {
-    "message": "to close",
-    "description": "The explanatory text of the action for Escape key"
-  },
-  "theme.SearchModal.footer.closeKeyAriaLabel": {
-    "message": "Escape key",
-    "description": "The ARIA label for the Escape key button that close the modal"
-  },
-  "theme.SearchModal.footer.searchByText": {
-    "message": "Search by",
-    "description": "The text explain that the search is making by Algolia"
-  },
-  "theme.SearchModal.noResultsScreen.noResultsText": {
-    "message": "No results for",
-    "description": "The text explains that there are no results for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.suggestedQueryText": {
-    "message": "Try searching for",
-    "description": "The text for the suggested query when no results are found for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsText": {
-    "message": "Believe this query should return results?",
-    "description": "The text for the question where the user thinks there are missing results"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
-    "message": "Let us know.",
-    "description": "The text for the link to report missing results"
-  },
-  "theme.SearchModal.placeholder": {
-    "message": "Search docs",
-    "description": "The placeholder of the input of the DocSearch pop-up modal"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Skip to main content",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Tags",
-    "description": "The title of the tag list page"
-  }
-}

docs/i18n/en/docusaurus-plugin-content-docs/current.json

@@ -1,6 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  }
-}

docs/i18n/en/docusaurus-theme-classic/footer.json

@@ -1,46 +0,0 @@
-{
-  "link.title.Pages": {
-    "message": "Pages",
-    "description": "The title of the footer links column with title=Pages in the footer"
-  },
-  "link.title.Community": {
-    "message": "Community",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.Translations": {
-    "message": "Translations",
-    "description": "The title of the footer links column with title=Translations in the footer"
-  },
-  "link.item.label.Installation": {
-    "message": "Installation",
-    "description": "The label of footer link with label=Installation linking to /installation/"
-  },
-  "link.item.label.Usage": {
-    "message": "Usage",
-    "description": "The label of footer link with label=Usage linking to /usage/"
-  },
-  "link.item.label.Donate": {
-    "message": "Donate",
-    "description": "The label of footer link with label=Donate linking to /donate/"
-  },
-  "link.item.label.GitHub": {
-    "message": "GitHub",
-    "description": "The label of footer link with label=GitHub linking to https://github.com/go-task/task"
-  },
-  "link.item.label.Twitter": {
-    "message": "Twitter",
-    "description": "The label of footer link with label=Twitter linking to https://twitter.com/taskfiledev"
-  },
-  "link.item.label.Mastodon": {
-    "message": "Mastodon",
-    "description": "The label of footer link with label=Mastodon linking to https://fosstodon.org/@task"
-  },
-  "link.item.label.Discord": {
-    "message": "Discord",
-    "description": "The label of footer link with label=Discord linking to https://discord.gg/6TY36E39UK"
-  },
-  "link.item.label.OpenCollective": {
-    "message": "OpenCollective",
-    "description": "The label of footer link with label=OpenCollective linking to https://opencollective.com/task"
-  }
-}

docs/i18n/en/docusaurus-theme-classic/navbar.json

@@ -1,38 +0,0 @@
-{
-  "title": {
-    "message": "Task",
-    "description": "The title in the navbar"
-  },
-  "item.label.Installation": {
-    "message": "Installation",
-    "description": "Navbar item with label Installation"
-  },
-  "item.label.Usage": {
-    "message": "Usage",
-    "description": "Navbar item with label Usage"
-  },
-  "item.label.API": {
-    "message": "API",
-    "description": "Navbar item with label API"
-  },
-  "item.label.Donate": {
-    "message": "Donate",
-    "description": "Navbar item with label Donate"
-  },
-  "item.label.GitHub": {
-    "message": "GitHub",
-    "description": "Navbar item with label GitHub"
-  },
-  "item.label.Twitter": {
-    "message": "Twitter",
-    "description": "Navbar item with label Twitter"
-  },
-  "item.label.Mastodon": {
-    "message": "Mastodon",
-    "description": "Navbar item with label Mastodon"
-  },
-  "item.label.Discord": {
-    "message": "Discord",
-    "description": "Navbar item with label Discord"
-  }
-}

docs/i18n/es-ES/code.json

@@ -1,396 +0,0 @@
-{
-  "theme.ErrorPageContent.title": {
-    "message": "Ha ocurrido un error con la página.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Volver a intentarlo",
-    "description": "The label of the button to try again when the page crashed"
-  },
-  "theme.NotFound.title": {
-    "message": "Página No Encontrada",
-    "description": "The title of the 404 page"
-  },
-  "theme.NotFound.p1": {
-    "message": "No pudimos encontrar lo que estabas buscando.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Por favor, contacta con el propietario del sitio al que está enlazada la URL original y comunícale que el enlace está roto.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.admonition.note": {
-    "message": "nota",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "pista",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.danger": {
-    "message": "peligro",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "información",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.caution": {
-    "message": "precaución",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Volver arriba",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archivo",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archivo",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Navegación por la página de la lista de blogs ",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Entradas más recientes",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Entradas antiguas",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Barra de paginación de publicaciones del blog",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Publicación más reciente",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Publicación más antigua",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.blog.post.plurals": {
-    "message": "Una publicación|{count} publicaciones",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} etiquetados con \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "Ver Todas las Etiquetas",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Cambiar entre modo oscuro y claro (actualmente {mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "modo oscuro",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "modo claro",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Página de inicio",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Breadcrumbs",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription": {
-    "message": "{count} items",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Navegación de páginas de documentos",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Anterior",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Siguiente",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "Un documento etiquetado|{count} documentos etiquetados",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} con \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Versión: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "Esta es documentación sin liberar para {siteTitle} {versionLabel} versión.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "Esta es documentación para {siteTitle} {versionLabel}, que ya no se mantiene activamente.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "Para la documentación actualizada, vea {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "última versión",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Editar esta página",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Enlace directo al {heading}",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " en {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " por {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Última actualización{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versiones",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Etiquetas:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Cerrar",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Navegación de publicaciones recientes",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copiado",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copiar código al portapapeles",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copiar",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Toggle word wrap",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.toggleCollapsedCategoryAriaLabel": {
-    "message": "Toggle the collapsible sidebar category '{label}'",
-    "description": "The ARIA label to toggle the collapsible sidebar category"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Languages",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "En esta página",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Leer Más",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Read more about {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "Lectura de un minuto|{readingTime} min de lectura",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Colapsar barra lateral",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Colapsar barra lateral",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Close navigation bar",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Volver al menú principal",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Toggle navigation bar",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expandir barra lateral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expandir barra lateral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.SearchBar.seeAll": {
-    "message": "See all {count} results"
-  },
-  "theme.SearchPage.documentsFound.plurals": {
-    "message": "Un documento encontrado|{count} documentos encontrados",
-    "description": "Pluralized label for \"{count} documents found\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.SearchPage.existingResultsTitle": {
-    "message": "Resultados de búsqueda para \"{query}\"",
-    "description": "The search page title for non-empty query"
-  },
-  "theme.SearchPage.emptyResultsTitle": {
-    "message": "Búsqueda en la documentación",
-    "description": "The search page title for empty query"
-  },
-  "theme.SearchPage.inputPlaceholder": {
-    "message": "Escribe tu búsqueda aquí",
-    "description": "The placeholder for search page input"
-  },
-  "theme.SearchPage.inputLabel": {
-    "message": "Buscar",
-    "description": "The ARIA label for search page input"
-  },
-  "theme.SearchPage.algoliaLabel": {
-    "message": "Búsqueda por Algolia",
-    "description": "The ARIA label for Algolia mention"
-  },
-  "theme.SearchPage.noResultsText": {
-    "message": "No se encontraron resultados",
-    "description": "The paragraph for empty search result"
-  },
-  "theme.SearchPage.fetchingNewResults": {
-    "message": "Obteniendo nuevos resultados...",
-    "description": "The paragraph for fetching new search results"
-  },
-  "theme.SearchBar.label": {
-    "message": "Buscar",
-    "description": "The ARIA label and placeholder for search button"
-  },
-  "theme.SearchModal.searchBox.resetButtonTitle": {
-    "message": "Clear the query",
-    "description": "The label and ARIA label for search box reset button"
-  },
-  "theme.SearchModal.searchBox.cancelButtonText": {
-    "message": "Cancel",
-    "description": "The label and ARIA label for search box cancel button"
-  },
-  "theme.SearchModal.startScreen.recentSearchesTitle": {
-    "message": "Recent",
-    "description": "The title for recent searches"
-  },
-  "theme.SearchModal.startScreen.noRecentSearchesText": {
-    "message": "No recent searches",
-    "description": "The text when no recent searches"
-  },
-  "theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
-    "message": "Save this search",
-    "description": "The label for save recent search button"
-  },
-  "theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
-    "message": "Remove this search from history",
-    "description": "The label for remove recent search button"
-  },
-  "theme.SearchModal.startScreen.favoriteSearchesTitle": {
-    "message": "Favorite",
-    "description": "The title for favorite searches"
-  },
-  "theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
-    "message": "Remove this search from favorites",
-    "description": "The label for remove favorite search button"
-  },
-  "theme.SearchModal.errorScreen.titleText": {
-    "message": "Unable to fetch results",
-    "description": "The title for error screen of search modal"
-  },
-  "theme.SearchModal.errorScreen.helpText": {
-    "message": "You might want to check your network connection.",
-    "description": "The help text for error screen of search modal"
-  },
-  "theme.SearchModal.footer.selectText": {
-    "message": "to select",
-    "description": "The explanatory text of the action for the enter key"
-  },
-  "theme.SearchModal.footer.selectKeyAriaLabel": {
-    "message": "Enter key",
-    "description": "The ARIA label for the Enter key button that makes the selection"
-  },
-  "theme.SearchModal.footer.navigateText": {
-    "message": "to navigate",
-    "description": "The explanatory text of the action for the Arrow up and Arrow down key"
-  },
-  "theme.SearchModal.footer.navigateUpKeyAriaLabel": {
-    "message": "Arrow up",
-    "description": "The ARIA label for the Arrow up key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.navigateDownKeyAriaLabel": {
-    "message": "Arrow down",
-    "description": "The ARIA label for the Arrow down key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.closeText": {
-    "message": "to close",
-    "description": "The explanatory text of the action for Escape key"
-  },
-  "theme.SearchModal.footer.closeKeyAriaLabel": {
-    "message": "Escape key",
-    "description": "The ARIA label for the Escape key button that close the modal"
-  },
-  "theme.SearchModal.footer.searchByText": {
-    "message": "Search by",
-    "description": "The text explain that the search is making by Algolia"
-  },
-  "theme.SearchModal.noResultsScreen.noResultsText": {
-    "message": "No results for",
-    "description": "The text explains that there are no results for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.suggestedQueryText": {
-    "message": "Try searching for",
-    "description": "The text for the suggested query when no results are found for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsText": {
-    "message": "Believe this query should return results?",
-    "description": "The text for the question where the user thinks there are missing results"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
-    "message": "Let us know.",
-    "description": "The text for the link to report missing results"
-  },
-  "theme.SearchModal.placeholder": {
-    "message": "Search docs",
-    "description": "The placeholder of the input of the DocSearch pop-up modal"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Saltar al contenido principal",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Etiquetas",
-    "description": "The title of the tag list page"
-  }
-}

docs/i18n/es-ES/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md

@@ -1,93 +0,0 @@
----
-title: Introducing Experiments
-description: A look at where task is, where it's going and how we're going to get there.
-slug: task-in-2023
-authors:
-  - pd93
-tags:
-  - experiments
-  - breaking-changes
-  - roadmap
-  - v4
-image: https://i.imgur.com/mErPwqL.png
-hide_table_of_contents: false
----
-
-Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
-
-<!--truncate-->
-
-## :calendar: So, what have we been up to?
-
-Over the past 12 months or so, [@andreynering][] (Author and maintainer of the project) and I ([@pd93][]) have been working in our spare time to maintain and improve v3 of Task and we've made some amazing progress. Here are just some of the things we've released in that time:
-
-- An official [extension for VS Code][vscode-task].
-- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
-- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
-- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
-- A series of refactors to the core codebase to make it more maintainable and extensible.
-- Loads of bug fixes and improvements.
-- An integration with [Crowdin][crowdin]. Work is in progress on making our docs available in **7 new languages** (Special thanks to all our translators for the huge help with this!).
-- And much, much more! :sparkles:
-
-We're also working on adding some really exciting and highly requested features to Task such as having the ability to run remote Taskfiles ([#1317](https://github.com/go-task/task/issues/1317)).
-
-None of this would have been possible without the [150 or so (and growing) contributors][contributors] to the project, numerous sponsors and a passionate community of users. Together we have more than doubled the number of GitHub stars to over 8400 :star: since the beginning of 2022 and this continues to accelerate. We can't thank you all enough for your help and support! :rocket:
-
-[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
-
-## What's next? :thinking:
-
-It's extremely motivating to see so many people using and loving Task. However, in this time we've also seen an increase in the number of issues and feature requests. In particular, issues that require some kind of breaking change to Task. This isn't a bad thing, but as we grow we need to be more responsible about how we address these changes in a way that ensures stability and compatibility for existing users and their Taskfiles.
-
-At this point you're probably thinking something like:
-
-> "But you use [semantic versioning][semver] - Just release a new major version with your breaking changes."
-
-And you'd be right... sort of. In theory, this sounds great, but the reality is that we don't have the time to commit to a major overhaul of Task in one big bang release. This would require a colossal amount of time and coordination and with full time jobs and personal lives to tend to, this is a difficult commitment to make. Smaller, more frequent major releases are also a significant inconvenience for users as they have to constantly keep up-to-date with our breaking changes. Fortunately, there is a better way.
-
-## What's going to change? :monocle:
-
-Going forwards, breaking changes will be allowed into _minor_ versions of Task as "experimental features". To access these features users will need opt-in by enabling feature flags. This will allow us to release new features slowly and gather feedback from the community before making them the default behavior in a future major release.
-
-To prepare users for the next major release, we will maintain a list of [deprecated features][deprecations] and [experiments][experiments] on our docs website and publish information on how to migrate to the new behavior.
-
-You can read the [full breaking change proposal][breaking-change-proposal] and view all the [current experiments and their status][experiments-project] on GitHub including the [Gentle Force][gentle-force-experiment] and [Remote Taskfiles][remote-taskfiles-experiment] experiments.
-
-## What will happen to v2/v3 features?
-
-v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase and focus on new functionality instead.
-
-When v4 is released, we will continue to support v3 for a period of time (bug fixes etc). However, since we are moving from a backward-compatibility model to a forwards-compatibility model, **v4 itself will not be backwards compatible with v3**.
-
-## v4 When? :eyes:
-
-:man_shrugging: When it's ready.
-
-In all seriousness, we don't have a timeline for this yet. We'll be working on the most serious deficiencies of the v3 API first and regularly evaluating the state of the project. When we feel its in a good, stable place and we have a clear upgrade path for users and a number of stable experiments, we'll start to think about v4.
-
-## :wave: Final thoughts
-
-Task is growing fast and we're excited to see where it goes next. We hope that the steps we're taking to improve the project and our process will help us to continue to grow. As always, if you have any questions or feedback, we encourage you to comment on or open [issues][issues] and [discussions][discussions] on GitHub. Alternatively, you can join us on [Discord][discord].
-
-I plan to write more of these blog posts in the future on a variety of Task-related topics, so make sure to check in occasionally and see what we're up to!
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[vscode-task]: https://github.com/go-task/vscode-task
-[crowdin]: https://crowdin.com
-[contributors]: https://github.com/go-task/task/graphs/contributors
-[semver]: https://semver.org
-[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
-[@andreynering]: https://github.com/andreynering
-[@pd93]: https://github.com/pd93
-[experiments]: https://taskfile.dev/experiments
-[deprecations]: https://taskfile.dev/deprecations
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
-[issues]: https://github.com/go-task/task/issues
-[discussions]: https://github.com/go-task/task/discussions
-[discord]: https://discord.gg/6TY36E39UK
-[experiments-project]: https://github.com/orgs/go-task/projects/1
-[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
-[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317

docs/i18n/es-ES/docusaurus-plugin-content-blog/authors.yml

@@ -1,10 +0,0 @@
-andreynering:
-  name: Andrey Nering
-  title: Maintainer of Task
-  url: https://github.com/andreynering
-  image_url: https://github.com/andreynering.png
-pd93:
-  name: Pete Davison
-  title: Maintainer of Task
-  url: https://github.com/pd93
-  image_url: https://github.com/pd93.png

docs/i18n/es-ES/docusaurus-plugin-content-docs/current.json

@@ -1,6 +0,0 @@
-{
-  "version.label": {
-    "message": "Siguiente",
-    "description": "The label for version current"
-  }
-}

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/api_reference.md

@@ -1,347 +0,0 @@
----
-slug: /api/
-sidebar_position: 4
-toc_min_heading_level: 2
-toc_max_heading_level: 5
----
-
-# API Reference
-
-## CLI
-
-Task command line tool has the following syntax:
-
-```bash
-task [--flags] [tasks...] [-- CLI_ARGS...]
-```
-
-:::tip
-
-If `--` is given, all remaining arguments will be assigned to a special `CLI_ARGS` variable
-
-:::
-
-| Short | Flag                        | Type     | Default                                      | Description                                                                                                                                                                                                    |
-| ----- | --------------------------- | -------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `-c`  | `--color`                   | `bool`   | `true`                                       | Colored output. Enabled by default. Set flag to `false` or use `NO_COLOR=1` to disable.                                                                                                                        |
-| `-C`  | `--concurrency`             | `int`    | `0`                                          | Limit number tasks to run concurrently. Zero means unlimited.                                                                                                                                                  |
-| `-d`  | `--dir`                     | `string` | Working directory                            | Sets directory of execution.                                                                                                                                                                                   |
-| `-n`  | `--dry`                     | `bool`   | `false`                                      | Compiles and prints tasks in the order that they would be run, without executing them.                                                                                                                         |
-| `-x`  | `--exit-code`               | `bool`   | `false`                                      | Pass-through the exit code of the task command.                                                                                                                                                                |
-| `-f`  | `--force`                   | `bool`   | `false`                                      | Forces execution even when the task is up-to-date.                                                                                                                                                             |
-| `-g`  | `--global`                  | `bool`   | `false`                                      | Runs global Taskfile, from `$HOME/Taskfile.{yml,yaml}`.                                                                                                                                                        |
-| `-h`  | `--help`                    | `bool`   | `false`                                      | Shows Task usage.                                                                                                                                                                                              |
-| `-i`  | `--init`                    | `bool`   | `false`                                      | Creates a new Taskfile.yml in the current folder.                                                                                                                                                              |
-| `-I`  | `--interval`                | `string` | `5s`                                         | Sets a different watch interval when using `--watch`, the default being 5 seconds. This string should be a valid [Go Duration](https://pkg.go.dev/time#ParseDuration).                                         |
-| `-l`  | `--list`                    | `bool`   | `false`                                      | Lists tasks with description of current Taskfile.                                                                                                                                                              |
-| `-a`  | `--list-all`                | `bool`   | `false`                                      | Lists tasks with or without a description.                                                                                                                                                                     |
-|       | `--sort`                    | `string` | `default`                                    | Changes the order of the tasks when listed.<br />`default` - Alphanumeric with root tasks first<br />`alphanumeric` - Alphanumeric<br />`none` - No sorting (As they appear in the Taskfile) |
-|       | `--json`                    | `bool`   | `false`                                      | See [JSON Output](#json-output)                                                                                                                                                                                |
-| `-o`  | `--output`                  | `string` | Default set in the Taskfile or `intervealed` | Sets output style: [`interleaved`/`group`/`prefixed`].                                                                                                                                                         |
-|       | `--output-group-begin`      | `string` |                                              | Message template to print before a task's grouped output.                                                                                                                                                      |
-|       | `--output-group-end`        | `string` |                                              | Message template to print after a task's grouped output.                                                                                                                                                       |
-|       | `--output-group-error-only` | `bool`   | `false`                                      | Swallow command output on zero exit code.                                                                                                                                                                      |
-| `-p`  | `--parallel`                | `bool`   | `false`                                      | Executes tasks provided on command line in parallel.                                                                                                                                                           |
-| `-s`  | `--silent`                  | `bool`   | `false`                                      | Disables echoing.                                                                                                                                                                                              |
-| `-y`  | `--yes`                     | `bool`   | `false`                                      | Assume "yes" as answer to all prompts.                                                                                                                                                                         |
-|       | `--status`                  | `bool`   | `false`                                      | Exits with non-zero exit code if any of the given tasks is not up-to-date.                                                                                                                                     |
-|       | `--summary`                 | `bool`   | `false`                                      | Show summary about a task.                                                                                                                                                                                     |
-| `-t`  | `--taskfile`                | `string` | `Taskfile.yml` or `Taskfile.yaml`            |                                                                                                                                                                                                                |
-| `-v`  | `--verbose`                 | `bool`   | `false`                                      | Enables verbose mode.                                                                                                                                                                                          |
-|       | `--version`                 | `bool`   | `false`                                      | Show Task version.                                                                                                                                                                                             |
-| `-w`  | `--watch`                   | `bool`   | `false`                                      | Enables watch of the given task.                                                                                                                                                                               |
-
-## Exit Codes
-
-Task will sometimes exit with specific exit codes. These codes are split into three groups with the following ranges:
-
-- General errors (0-99)
-- Taskfile errors (100-199)
-- Task errors (200-299)
-
-A full list of the exit codes and their descriptions can be found below:
-
-| Code | Description                                                  |
-| ---- | ------------------------------------------------------------ |
-| 0    | Success                                                      |
-| 1    | An unknown error occurred                                    |
-| 100  | No Taskfile was found                                        |
-| 101  | A Taskfile already exists when trying to initialize one      |
-| 102  | The Taskfile is invalid or cannot be parsed                  |
-| 103  | A remote Taskfile could not be downloaded                    |
-| 104  | A remote Taskfile was not trusted by the user                |
-| 105  | A remote Taskfile was could not be fetched securely          |
-| 106  | No cache was found for a remote Taskfile in offline mode     |
-| 107  | No schema version was defined in the Taskfile                |
-| 200  | The specified task could not be found                        |
-| 201  | An error occurred while executing a command inside of a task |
-| 202  | The user tried to invoke a task that is internal             |
-| 203  | There a multiple tasks with the same name or alias           |
-| 204  | A task was called too many times                             |
-| 205  | A task was cancelled by the user                             |
-| 206  | A task was not executed due to missing required variables    |
-
-These codes can also be found in the repository in [`errors/errors.go`](https://github.com/go-task/task/blob/main/errors/errors.go).
-
-:::info
-
-When Task is run with the `-x`/`--exit-code` flag, the exit code of any failed commands will be passed through to the user instead.
-
-:::
-
-## JSON Output
-
-When using the `--json` flag in combination with either the `--list` or `--list-all` flags, the output will be a JSON object with the following structure:
-
-```json
-{
-  "tasks": [
-    {
-      "name": "",
-      "desc": "",
-      "summary": "",
-      "up_to_date": false,
-      "location": {
-        "line": 54,
-        "column": 3,
-        "taskfile": "/path/to/Taskfile.yml"
-      }
-    }
-    // ...
-  ],
-  "location": "/path/to/Taskfile.yml"
-}
-```
-
-## Special Variables
-
-There are some special variables that is available on the templating system:
-
-| Var                | Description                                                                                                                                              |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CLI_ARGS`         | Contain all extra arguments passed after `--` when calling Task through the CLI.                                                                         |
-| `CLI_FORCE`        | A boolean containing whether the `--force` or `--force-all` flags were set.                                                                              |
-| `TASK`             | The name of the current task.                                                                                                                            |
-| `ROOT_DIR`         | The absolute path of the root Taskfile.                                                                                                                  |
-| `TASKFILE_DIR`     | The absolute path of the included Taskfile.                                                                                                              |
-| `USER_WORKING_DIR` | The absolute path of the directory `task` was called from.                                                                                               |
-| `CHECKSUM`         | The checksum of the files listed in `sources`. Only available within the `status` prop and if method is set to `checksum`.                               |
-| `TIMESTAMP`        | The date object of the greatest timestamp of the files listed in `sources`. Only available within the `status` prop and if method is set to `timestamp`. |
-| `TASK_VERSION`     | The current version of task.                                                                                                                             |
-| `ITEM`             | The value of the current iteration when using the `for` property. Can be changed to a different variable name using `as:`.                               |
-
-## ENV
-
-Some environment variables can be overridden to adjust Task behavior.
-
-| ENV                  | Default | Description                                                                                                       |
-| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------- |
-| `TASK_TEMP_DIR`      | `.task` | Location of the temp dir. Can relative to the project like `tmp/task` or absolute like `/tmp/.task` or `~/.task`. |
-| `TASK_COLOR_RESET`   | `0`     | Color used for white.                                                                                             |
-| `TASK_COLOR_BLUE`    | `34`    | Color used for blue.                                                                                              |
-| `TASK_COLOR_GREEN`   | `32`    | Color used for green.                                                                                             |
-| `TASK_COLOR_CYAN`    | `36`    | Color used for cyan.                                                                                              |
-| `TASK_COLOR_YELLOW`  | `33`    | Color used for yellow.                                                                                            |
-| `TASK_COLOR_MAGENTA` | `35`    | Color used for magenta.                                                                                           |
-| `TASK_COLOR_RED`     | `31`    | Color used for red.                                                                                               |
-| `FORCE_COLOR`        |         | Force color output usage.                                                                                         |
-
-## Taskfile Schema
-
-| Attribute  | Type                               | Default       | Description                                                                                                                                                            |
-| ---------- | ---------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `version`  | `string`                           |               | Version of the Taskfile. The current version is `3`.                                                                                                                   |
-| `output`   | `string`                           | `interleaved` | Output mode. Available options: `interleaved`, `group` and `prefixed`.                                                                                                 |
-| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overridden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                     |
-| `includes` | [`map[string]Include`](#include)   |               | Additional Taskfiles to be included.                                                                                                                                   |
-| `vars`     | [`map[string]Variable`](#variable) |               | A set of global variables.                                                                                                                                             |
-| `env`      | [`map[string]Variable`](#variable) |               | A set of global environment variables.                                                                                                                                 |
-| `tasks`    | [`map[string]Task`](#task)         |               | A set of task definitions.                                                                                                                                             |
-| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overridden with `true` in a task by task basis.                                                         |
-| `dotenv`   | `[]string`                         |               | A list of `.env` file paths to be parsed.                                                                                                                              |
-| `run`      | `string`                           | `always`      | Default 'run' option for this Taskfile. Available options: `always`, `once` and `when_changed`.                                                                        |
-| `interval` | `string`                           | `5s`          | Sets a different watch interval when using `--watch`, the default being 5 seconds. This string should be a valid [Go Duration](https://pkg.go.dev/time#ParseDuration). |
-| `set`      | `[]string`                         |               | Specify options for the [`set` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html).                                                      |
-| `shopt`    | `[]string`                         |               | Specify option for the [`shopt` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html).                                                   |
-
-### Include
-
-| Attribute  | Type                  | Default                       | Description                                                                                                                                                                                                                                              |
-| ---------- | --------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `taskfile` | `string`              |                               | The path for the Taskfile or directory to be included. If a directory, Task will look for files named `Taskfile.yml` or `Taskfile.yaml` inside that directory. If a relative path, resolved relative to the directory containing the including Taskfile. |
-| `dir`      | `string`              | The parent Taskfile directory | The working directory of the included tasks when run.                                                                                                                                                                                                    |
-| `optional` | `bool`                | `false`                       | If `true`, no errors will be thrown if the specified file does not exist.                                                                                                                                                                                |
-| `internal` | `bool`                | `false`                       | Stops any task in the included Taskfile from being callable on the command line. These commands will also be omitted from the output when used with `--list`.                                                                                            |
-| `aliases`  | `[]string`            |                               | Alternative names for the namespace of the included Taskfile.                                                                                                                                                                                            |
-| `vars`     | `map[string]Variable` |                               | A set of variables to apply to the included Taskfile.                                                                                                                                                                                                    |
-
-:::info
-
-Informing only a string like below is equivalent to setting that value to the `taskfile` attribute.
-
-```yaml
-includes:
-  foo: ./path
-```
-
-:::
-
-### Variable
-
-| Attribute | Type     | Default | Description                                                              |
-| --------- | -------- | ------- | ------------------------------------------------------------------------ |
-| _itself_  | `string` |         | A static value that will be set to the variable.                         |
-| `sh`      | `string` |         | A shell command. The output (`STDOUT`) will be assigned to the variable. |
-
-:::info
-
-Static and dynamic variables have different syntaxes, like below:
-
-```yaml
-vars:
-  STATIC: static
-  DYNAMIC:
-    sh: echo "dynamic"
-```
-
-:::
-
-### Task
-
-| Attribute       | Type                               | Default                                               | Description                                                                                                                                                                                                                                                                                              |
-| --------------- | ---------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cmds`          | [`[]Command`](#command)            |                                                       | A list of shell commands to be executed.                                                                                                                                                                                                                                                                 |
-| `deps`          | [`[]Dependency`](#dependency)      |                                                       | A list of dependencies of this task. Tasks defined here will run in parallel before this task.                                                                                                                                                                                                           |
-| `label`         | `string`                           |                                                       | Overrides the name of the task in the output when a task is run. Supports variables.                                                                                                                                                                                                                     |
-| `desc`          | `string`                           |                                                       | A short description of the task. This is displayed when calling `task --list`.                                                                                                                                                                                                                           |
-| `prompt`        | `string`                           |                                                       | A prompt that will be presented before a task is run. Declining will cancel running the current and any subsequent tasks.                                                                                                                                                                                |
-| `summary`       | `string`                           |                                                       | A longer description of the task. This is displayed when calling `task --summary [task]`.                                                                                                                                                                                                                |
-| `aliases`       | `[]string`                         |                                                       | A list of alternative names by which the task can be called.                                                                                                                                                                                                                                             |
-| `sources`       | `[]string`                         |                                                       | A list of sources to check before running this task. Relevant for `checksum` and `timestamp` methods. Can be file paths or star globs.                                                                                                                                                                   |
-| `generates`     | `[]string`                         |                                                       | A list of files meant to be generated by this task. Relevant for `timestamp` method. Can be file paths or star globs.                                                                                                                                                                                    |
-| `status`        | `[]string`                         |                                                       | A list of commands to check if this task should run. The task is skipped otherwise. This overrides `method`, `sources` and `generates`.                                                                                                                                                                  |
-| `requires`      | `[]string`                         |                                                       | A list of variables which should be set if this task is to run, if any of these variables are unset the task will error and not run.                                                                                                                                                                     |
-| `preconditions` | [`[]Precondition`](#precondition)  |                                                       | A list of commands to check if this task should run. If a condition is not met, the task will error.                                                                                                                                                                                                     |
-| `requires`      | [`Requires`](#requires)            |                                                       | A list of required variables which should be set if this task is to run, if any variables listed are unset the task will error and not run.                                                                                                                                                              |
-| `dir`           | `string`                           |                                                       | The directory in which this task should run. Defaults to the current working directory.                                                                                                                                                                                                                  |
-| `vars`          | [`map[string]Variable`](#variable) |                                                       | A set of variables that can be used in the task.                                                                                                                                                                                                                                                         |
-| `env`           | [`map[string]Variable`](#variable) |                                                       | A set of environment variables that will be made available to shell commands.                                                                                                                                                                                                                            |
-| `dotenv`        | `[]string`                         |                                                       | A list of `.env` file paths to be parsed.                                                                                                                                                                                                                                                                |
-| `silent`        | `bool`                             | `false`                                               | Hides task name and command from output. The command's output will still be redirected to `STDOUT` and `STDERR`. When combined with the `--list` flag, task descriptions will be hidden.                                                                                                                 |
-| `interactive`   | `bool`                             | `false`                                               | Tells task that the command is interactive.                                                                                                                                                                                                                                                              |
-| `internal`      | `bool`                             | `false`                                               | Stops a task from being callable on the command line. It will also be omitted from the output when used with `--list`.                                                                                                                                                                                   |
-| `method`        | `string`                           | `checksum`                                            | Defines which method is used to check the task is up-to-date. `timestamp` will compare the timestamp of the sources and generates files. `checksum` will check the checksum (You probably want to ignore the .task folder in your .gitignore file). `none` skips any validation and always run the task. |
-| `prefix`        | `string`                           |                                                       | Defines a string to prefix the output of tasks running in parallel. Only used when the output mode is `prefixed`.                                                                                                                                                                                        |
-| `ignore_error`  | `bool`                             | `false`                                               | Continue execution if errors happen while executing commands.                                                                                                                                                                                                                                            |
-| `run`           | `string`                           | The one declared globally in the Taskfile or `always` | Specifies whether the task should run again or not if called more than once. Available options: `always`, `once` and `when_changed`.                                                                                                                                                                     |
-| `platforms`     | `[]string`                         | All platforms                                         | Specifies which platforms the task should be run on. [Valid GOOS and GOARCH values allowed](https://github.com/golang/go/blob/main/src/go/build/syslist.go). Task will be skipped otherwise.                                                                                                             |
-| `set`           | `[]string`                         |                                                       | Specify options for the [`set` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html).                                                                                                                                                                                        |
-| `shopt`         | `[]string`                         |                                                       | Specify option for the [`shopt` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html).                                                                                                                                                                                     |
-
-:::info
-
-These alternative syntaxes are available. They will set the given values to `cmds` and everything else will be set to their default values:
-
-```yaml
-tasks:
-  foo: echo "foo"
-
-  foobar:
-    - echo "foo"
-    - echo "bar"
-
-  baz:
-    cmd: echo "baz"
-```
-
-:::
-
-#### Command
-
-| Attribute      | Type                               | Default       | Description                                                                                                                                                                                        |
-| -------------- | ---------------------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cmd`          | `string`                           |               | The shell command to be executed.                                                                                                                                                                  |
-| `task`         | `string`                           |               | Set this to trigger execution of another task instead of running a command. This cannot be set together with `cmd`.                                                                                |
-| `for`          | [`For`](#for)                      |               | Runs the command once for each given value.                                                                                                                                                        |
-| `silent`       | `bool`                             | `false`       | Skips some output for this command. Note that STDOUT and STDERR of the commands will still be redirected.                                                                                          |
-| `vars`         | [`map[string]Variable`](#variable) |               | Optional additional variables to be passed to the referenced task. Only relevant when setting `task` instead of `cmd`.                                                                             |
-| `ignore_error` | `bool`                             | `false`       | Continue execution if errors happen while executing the command.                                                                                                                                   |
-| `defer`        | `string`                           |               | Alternative to `cmd`, but schedules the command to be executed at the end of this task instead of immediately. This cannot be used together with `cmd`.                                            |
-| `platforms`    | `[]string`                         | All platforms | Specifies which platforms the command should be run on. [Valid GOOS and GOARCH values allowed](https://github.com/golang/go/blob/main/src/go/build/syslist.go). Command will be skipped otherwise. |
-| `set`          | `[]string`                         |               | Specify options for the [`set` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html).                                                                                  |
-| `shopt`        | `[]string`                         |               | Specify option for the [`shopt` builtin](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html).                                                                               |
-
-:::info
-
-If given as a a string, the value will be assigned to `cmd`:
-
-```yaml
-tasks:
-  foo:
-    cmds:
-      - echo "foo"
-      - echo "bar"
-```
-
-:::
-
-#### Dependency
-
-| Attribute | Type                               | Default | Description                                                                                                      |
-| --------- | ---------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------- |
-| `task`    | `string`                           |         | The task to be execute as a dependency.                                                                          |
-| `vars`    | [`map[string]Variable`](#variable) |         | Optional additional variables to be passed to this task.                                                         |
-| `silent`  | `bool`                             | `false` | Hides task name and command from output. The command's output will still be redirected to `STDOUT` and `STDERR`. |
-
-:::tip
-
-If you don't want to set additional variables, it's enough to declare the dependency as a list of strings (they will be assigned to `task`):
-
-```yaml
-tasks:
-  foo:
-    deps: [foo, bar]
-```
-
-:::
-
-#### For
-
-The `for` parameter can be defined as a string, a list of strings or a map. If it is defined as a string, you can give it any of the following values:
-
-- `source` - Will run the command for each source file defined on the task. (Glob patterns will be resolved, so `*.go` will run for every Go file that matches).
-
-If it is defined as a list of strings, the command will be run for each value.
-
-Finally, the `for` parameter can be defined as a map when you want to use a variable to define the values to loop over:
-
-| Attribute | Type     | Default          | Description                                  |
-| --------- | -------- | ---------------- | -------------------------------------------- |
-| `var`     | `string` |                  | The name of the variable to use as an input. |
-| `split`   | `string` | (any whitespace) | What string the variable should be split on. |
-| `as`      | `string` | `ITEM`           | The name of the iterator variable.           |
-
-#### Precondition
-
-| Attribute | Type     | Default | Description                                                                                                  |
-| --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------ |
-| `sh`      | `string` |         | Command to be executed. If a non-zero exit code is returned, the task errors without executing its commands. |
-| `msg`     | `string` |         | Optional message to print if the precondition isn't met.                                                     |
-
-:::tip
-
-If you don't want to set a different message, you can declare a precondition like this and the value will be assigned to `sh`:
-
-```yaml
-tasks:
-  foo:
-    precondition: test -f Taskfile.yml
-```
-
-:::
-
-#### Requires
-
-| Attribute | Type       | Default | Description                                                                                        |
-| --------- | ---------- | ------- | -------------------------------------------------------------------------------------------------- |
-| `vars`    | `[]string` |         | List of variable or environment variable names that must be set if this task is to execute and run |

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/changelog.md

@@ -1,573 +0,0 @@
----
-slug: /changelog/
-sidebar_position: 14
----
-
-# Changelog
-
-## v3.33.1 - 2023-12-21
-
-- Added support for looping over map variables with the [Any Variables experiment](https://taskfile.dev/experiments/any_variables) enabled (#1435, #1437 by @pd93).
-- Fixed a bug where dynamic variables were causing errors during fast compilation (#1435, #1437 by @pd93)
-
-## v3.33.0 - 2023-12-20
-
-- Added [Any Variables experiment](https://taskfile.dev/experiments/any-variables) (#1415, #1421 by @pd93).
-- Updated Docusaurus to v3 (#1432 by @pd93).
-- Added `aliases` to `--json` flag output (#1430, #1431 by @pd93).
-- Added new `CLI_FORCE` special variable containing whether the `--force` or `--force-all` flags were set (#1412, #1434 by @pd93).
-
-## v3.32.0 - 2023-11-29
-
-- Added ability to exclude some files from `sources:` by using `exclude:` (#225,
-
-  # 1324 by @pd93 and @andreynering).
-- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default (#1317, #1345 by @pd93).
-- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1345 by @pd93).
-- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` (#1273, #1377 by @andreynering).
-- Fix `schema.json` to make `silent` valid in `cmds` that use `for` (#1385,
-
-  # 1386 by @iainvm).
-- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` (#1348, #1368 by @amancevice).
-
-## v3.31.0 - 2023-10-07
-
-- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1344 by @pd93).
-- Add ability to set `watch: true` in a task to automatically run it in watch mode (#231, #1361 by @andreynering).
-- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored (#1356 by @butuzov).
-- Fixed a nil pointer error when running a Taskfile with no contents (#1341,
-
-  # 1342 by @pd93).
-- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version (#1342 by @pd93).
-- Increased limit of maximum task calls from 100 to 1000 for now, as some people have been reaching this limit organically now that we have loops. This check exists to detect recursive calls, but will be removed in favor of a better algorithm soon (#1321, #1332).
-- Fixed templating on descriptions on `task --list` (#1343 by @blackjid).
-- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted (#1337, #1338 by @sylv-io).
-
-## v3.30.1 - 2023-09-14
-
-- Fixed a regression where some special variables weren't being set correctly (#1331, #1334 by @pd93).
-
-## v3.30.0 - 2023-09-13
-
-- Prep work for Remote Taskfiles (#1316 by @pd93).
-- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft (#1152, #1317 by @pd93).
-- Improve performance of content checksuming on `sources:` by replacing md5 with [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking change because checksums will be invalidated when upgrading to this release (#1325 by @ReillyBrogan).
-
-## v3.29.1 - 2023-08-26
-
-- Update to Go 1.21 (bump minimum version to 1.20) (#1302 by @pd93)
-- Fix a missing a line break on log when using `--watch` mode (#1285, #1297 by @FilipSolich).
-- Fix `defer` on JSON Schema (#1288 by @calvinmclean and @andreynering).
-- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` (#1046, #1205, #1250, #1293, #1312, #1274 by @andarto, #1309 by @andreynering).
-- Fix bug on `--status` flag. Running this flag should not have side-effects: it should not update the checksum on `.task`, only report its status (#1305,
-
-  # 1307 by @visciang, #1313 by @andreynering).
-
-## v3.28.0 - 2023-07-24
-
-- Added the ability to [loop over commands and tasks](https://taskfile.dev/usage/#looping-over-values) using `for` (#82, #1220 by @pd93).
-- Fixed variable propagation in multi-level includes (#778, #996, #1256 by @hudclark).
-- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly (#1266, #1270 by @pd93).
-- Fixed a `nil` panic when a dependency was commented out or left empty (#1263 by @neomantra).
-
-## v3.27.1 - 2023-06-30
-
-- Fix panic when a `.env` directory (not file) is present on current directory (#1244, #1245 by @pd93).
-
-## v3.27.0 - 2023-06-29
-
-- Allow Taskfiles starting with lowercase characters (#947, #1221 by @pd93).
-  - e.g. `taskfile.yml`, `taskfile.yaml`, `taskfile.dist.yml` & `taskfile.dist.yaml`
-- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). (#1190, by @sounisi5011).
-- Added the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) as a draft (#1200, #1216 by @pd93).
-- Added an `--experiments` flag to allow you to see which experiments are enabled (#1242 by @pd93).
-- Added ability to specify which variables are required in a task (#1203, #1204 by @benc-uk).
-
-## v3.26.0 - 2023-06-10
-
-- Only rewrite checksum files in `.task` if the checksum has changed (#1185,
-
-  # 1194 by @deviantintegral).
-- Added [experiments documentation](https://taskfile.dev/experiments) to the website (#1198 by @pd93).
-- Deprecated `version: 2` schema. This will be removed in the next major release (#1197, #1198, #1199 by @pd93).
-- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task (#100, #1163 by @MaxCheetham, [Documentation](https://taskfile.dev/usage/#warning-prompts)).
-- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task (#1130, #1131 by @timdp).
-
-## v3.25.0 - 2023-05-22
-
-- Support `silent:` when calling another tasks (#680, #1142 by @danquah).
-- Improve PowerShell completion script (#1168 by @trim21).
-- Add more languages to the website menu and show translation progress percentage (#1173 by @misitebao).
-- Starting on this release, official binaries for FreeBSD will be available to download (#1068 by @andreynering).
-- Fix some errors being unintendedly supressed (#1134 by @clintmod).
-- Fix a nil pointer error when `version` is omitted from a Taskfile (#1148,
-
-  # 1149 by @pd93).
-- Fix duplicate error message when a task does not exists (#1141, #1144 by @pd93).
-
-## v3.24.0 - 2023-04-15
-
-- Fix Fish shell completion for tasks with aliases (#1113 by @patricksjackson).
-- The default branch was renamed from `master` to `main` (#1049, #1048 by @pd93).
-- Fix bug where "up-to-date" logs were not being omitted for silent tasks (#546,
-
-  # 1107 by @danquah).
-- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` (#1098 by @misery).
-- More improvements to the release tool (#1096 by @pd93).
-- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter (#1099 by @pd93)
-- Add `--sort` flag for use with `--list` and `--list-all` (#946, #1105 by @pd93).
-- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error (#1114 by @pd93).
-
-## v3.23.0 - 2023-03-26
-
-Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by @pd93! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
-
-> **NOTE:** The extension _requires_ v3.23.0 to be installed in order to work.
-
-- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available (#1057, #1058 by @misitebao).
-- Added task location data to the `--json` flag output (#1056 by @pd93)
-- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` (#1062 by @misitebao).
-- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments (#1040, #1059 by @dhanusaputra).
-- Fix the value of `{{.CHECKSUM}}` variable in status (#1076, #1080 by @pd93).
-- Fixed deep copy implementation (#1072 by @pd93)
-- Created a tool to assist with releases (#1086 by @pd93).
-
-## v3.22.0 - 2023-03-10
-
-- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), #1029 by @andreynering).
-- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code (#664, #1022 by @jaedle).
-- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` (#840, #1035 by @harelwa, #1037 by @pd93).
-- Refactored and decoupled fingerprinting from the main Task executor (#1039 by @pd93).
-- Fixed deadlock issue when using `run: once` (#715, #1025 by @theunrepentantgeek).
-
-## v3.21.0 - 2023-02-22
-
-- Added new `TASK_VERSION` special variable (#990, #1014 by @ja1code).
-- Fixed a bug where tasks were sometimes incorrectly marked as internal (#1007 by @pd93).
-- Update to Go 1.20 (bump minimum version to 1.19) (#1010 by @pd93)
-- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY (#1003 by @automation-stack)
-
-## v3.20.0 - 2023-01-14
-
-- Improve behavior and performance of status checking when using the `timestamp` mode (#976, #977 by @aminya).
-- Performance optimizations were made for large Taskfiles (#982 by @pd93).
-- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins (#908, #929 by @pd93, [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
-- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped (#978, #980 by @leaanthony).
-
-## v3.19.1 - 2022-12-31
-
-- Small bug fix: closing `Taskfile.yml` once we're done reading it (#963, #964 by @HeCorr).
-- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file (#961, #971 by @pd93).
-- Fixed a bug where watch intervals set in the Taskfile were not being respected (#969, #970 by @pd93)
-- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future (#936 by @davidalpert, #764).
-
-## v3.19.0 - 2022-12-05
-
-- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm#2](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm#3](https://github.com/go-task/go-npm/pull/3)).
-- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos (#289, #920).
-- Add task-level `dotenv` support (#389, #904).
-- It's now possible to use global level variables on `includes` (#942, #943).
-- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [@DeronW](https://github.com/DeronW). Thanks!
-
-## v3.18.0 - 2022-11-12
-
-- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts (#919).
-- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output (#806, #890).
-- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` (#661, #815).
-
-## v3.17.0 - 2022-10-14
-
-- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found (#867, #880).
-- Now YAML parse errors will print which Taskfile failed to parse (#885, #887).
-- Add ability to set `aliases` for tasks and namespaces (#268, #340, #879).
-- Improvements to Fish shell completion (#897).
-- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag (#813, #865).
-- Add colored output to `--list`, `--list-all` and `--summary` flags (#845,
-
-  # 874).
-- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` (#603, #877).
-
-## v3.16.0 - 2022-09-29
-
-- Add `npm` as new installation method: `npm i -g @go-task/cli` (#870, #871, [npm package](https://www.npmjs.com/package/@go-task/cli)).
-- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` (#818).
-
-## v3.15.2 - 2022-09-08
-
-- Fix error when using variable in `env:` introduced in the previous release (#858, #866).
-- Fix handling of `CLI_ARGS` (`--`) in Bash completion (#863).
-- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion (#861).
-
-## v3.15.0 - 2022-09-03
-
-- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature (#215, #857, [Documentation](https://taskfile.dev/api/#special-variables)).
-- Follow symlinks on `sources` (#826, #831).
-- Improvements and fixes to Bash completion (#835, #844).
-
-## v3.14.1 - 2022-08-03
-
-- Always resolve relative include paths relative to the including Taskfile (#822, #823).
-- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) (#803).
-
-## v3.14.0 - 2022-07-08
-
-- Add ability to override the `.task` directory location with the `TASK_TEMP_DIR` environment variable.
-- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` (#568, #792).
-- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order (#779).
-- Starting on this release, ARM architecture binaries are been released to Snap as well (#795).
-- i386 binaries won't be available anymore on Snap because Ubuntu removed the support for this architecture.
-- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays (#785, [mvdan/sh#884](https://github.com/mvdan/sh/issues/884), [mvdan/sh#893](https://github.com/mvdan/sh/pull/893)).
-
-## v3.13.0 - 2022-06-13
-
-- Added `-n` as an alias to `--dry` (#776, #777).
-- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work (#458, #479, #728, #769).
-- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran (#755).
-
-## v3.12.1 - 2022-05-10
-
-- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` (#717).
-
-## v3.12.0 - 2022-03-31
-
-- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description (#691).
-- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level (#390, #623, #656).
-- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information (#677).
-
-## v3.11.0 - 2022-02-19
-
-- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information (#647, #651).
-- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information (#498, #666).
-
-## v3.10.0 - 2022-01-04
-
-- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description (#383, #401).
-- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer),
-
-  # 475, #626).
-- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix (#642, #644, #645).
-- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! (#183, #184, #369, #584,
-
-  # 621).
-- Fixed error when computing a variable when the task directory do not exist yet (#481, #579).
-
-## v3.9.2 - 2021-12-02
-
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows (#619, [mvdan/sh#768](https://github.com/mvdan/sh/issues/768), [mvdan/sh#769](https://github.com/mvdan/sh/pull/769)).
-
-## v3.9.1 - 2021-11-28
-
-- Add logging in verbose mode for when a task starts and finishes (#533, #588).
-- Fix an issue with preconditions and context errors (#597, #598).
-- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many (#613).
-- Fix nil pointer when `cmd:` was left empty (#612, #614).
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains two relevant fixes:
-  - Fix quote of empty strings in `shellQuote` (#609, [mvdan/sh#763](https://github.com/mvdan/sh/issues/763)).
-  - Fix issue of wrong environment variable being picked when there's another very similar one (#586, [mvdan/sh#745](https://github.com/mvdan/sh/pull/745)).
-- Install shell completions automatically when installing via Homebrew (#264, #592, [go-task/homebrew-tap#2](https://github.com/go-task/homebrew-tap/pull/2)).
-
-## v3.9.0 - 2021-10-02
-
-- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh#727](https://github.com/mvdan/sh/pull/727), [mvdan/sh#737](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3@v3.4.0/syntax#Quote))
-- In this version [mvdan.cc/sh](https://github.com/mvdan/sh) was upgraded with some small fixes and features
-  - The `read -p` flag is now supported (#314, [mvdan/sh#551](https://github.com/mvdan/sh/issues/551), [mvdan/sh#772](https://github.com/mvdan/sh/pull/722))
-  - The `pwd -P` and `pwd -L` flags are now supported (#553, [mvdan/sh#724](https://github.com/mvdan/sh/issues/724), [mvdan/sh#728](https://github.com/mvdan/sh/pull/728))
-  - The `$GID` environment variable is now correctly being set (#561, [mvdan/sh#723](https://github.com/mvdan/sh/pull/723))
-
-## v3.8.0 - 2021-09-26
-
-- Add `interactive: true` setting to improve support for interactive CLI apps (#217, #563).
-- Fix some `nil` errors (#534, #573).
-- Add ability to declare an included Taskfile as optional (#519, #552).
-- Add support for including Taskfiles in the home directory by using `~` (#539, #557).
-
-## v3.7.3 - 2021-09-04
-
-- Add official support to Apple M1 (#564, #567).
-- Our [official Homebrew tap](https://github.com/go-task/homebrew-tap) will support more platforms, including Apple M1
-
-## v3.7.0 - 2021-07-31
-
-- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! (#53, #359).
-
-## v3.6.0 - 2021-07-10
-
-- Allow using both `sources:` and `status:` in the same task (#411, #427, #477).
-- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` (#517).
-
-## v3.5.0 - 2021-07-04
-
-- Add support for interpolation in `dotenv:` (#433, #434, #453).
-
-## v3.4.3 - 2021-05-30
-
-- Add support for the `NO_COLOR` environment variable. (#459, [fatih/color#137](https://github.com/fatih/color/pull/137)).
-- Fix bug where sources were not considering the right directory in `--watch` mode (#484, #485).
-
-## v3.4.2 - 2021-04-23
-
-- On watch, report which file failed to read (#472).
-- Do not try to catch SIGKILL signal, which are not actually possible (#476).
-- Improve version reporting when building Task from source using Go Modules (#462, #473).
-
-## v3.4.1 - 2021-04-17
-
-- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example (#467).
-- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code (#135).
-- Print task name before the command in the log output (#398).
-
-## v3.3.0 - 2021-03-20
-
-- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable (#327).
-- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. (#345).
-
-## v3.2.2 - 2021-01-12
-
-- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags (#332).
-- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment (#425).
-- Fixed environment from .env files not being available as variables (#379).
-- The install script is now working for ARM platforms (#428).
-
-## v3.2.1 - 2021-01-09
-
-- Fixed some bugs and regressions regarding dynamic variables and directories (#426).
-- The [slim-sprig](https://github.com/go-task/slim-sprig) package was updated with the upstream [sprig](https://github.com/Masterminds/sprig).
-
-## v3.2.0 - 2021-01-07
-
-- Fix the `.task` directory being created in the task directory instead of the Taskfile directory (#247).
-- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile (#384).
-- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now (#423, #365).
-
-## v3.1.0 - 2021-01-03
-
-- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute (#412).
-- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux (#375, #418).
-- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them (#393).
-- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line (#403).
-
-## v3.0.1 - 2020-12-26
-
-- Allow use as a library by moving the required packages out of the `internal` directory (#358).
-- Do not error if a specified dotenv file does not exist (#378, #385).
-- Fix panic when you have empty tasks in your Taskfile (#338, #362).
-
-## v3.0.0 - 2020-08-16
-
-- On `v3`, all CLI variables will be considered global variables (#336, #341)
-- Add support to `.env` like files (#324, #356).
-- Add `label:` to task so you can override the task name in the logs (#321,
-
-  # 337).
-- Refactor how variables work on version 3 (#311).
-- Disallow `expansions` on v3 since it has no effect.
-- `Taskvars.yml` is not automatically included anymore.
-- `Taskfile_{{OS}}.yml` is not automatically included anymore.
-- Allow interpolation on `includes`, so you can manually include a Taskfile based on operation system, for example.
-- Expose `.TASK` variable in templates with the task name (#252).
-- Implement short task syntax (#194, #240).
-- Added option to make included Taskfile run commands on its own directory (#260, #144)
-- Taskfiles in version 1 are not supported anymore (#237).
-- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile (#246).
-- Changed default method from `timestamp` to `checksum` (#246).
-- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` (#216).
-- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% (#219).
-- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc (#207).
-
-## v2.8.1 - 2020-05-20
-
-- Fix error code for the `--help` flag (#300, #330).
-- Print version to stdout instead of stderr (#299, #329).
-- Supress `context` errors when using the `--watch` flag (#313, #317).
-- Support templating on description (#276, #283).
-
-## v2.8.0 - 2019-12-07
-
-- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel (#266).
-- Fixed bug where calling the `task` CLI only informing global vars would not execute the `default` task.
-- Add hability to silent all tasks by adding `silent: true` a the root of the Taskfile.
-
-## v2.7.1 - 2019-11-10
-
-- Fix error being raised when `exit 0` was called (#251).
-
-## v2.7.0 - 2019-09-22
-
-- Fixed panic bug when assigning a global variable (#229, #243).
-- A task with `method: checksum` will now re-run if generated files are deleted (#228, #238).
-
-## v2.6.0 - 2019-07-21
-
-- Fixed some bugs regarding minor version checks on `version:`.
-- Add `preconditions:` to task (#205).
-- Create directory informed on `dir:` if it doesn't exist (#209, #211).
-- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) (#221).
-- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap#1](https://github.com/go-task/homebrew-tap/pull/1)).
-
-## v2.5.2 - 2019-05-11
-
-- Reverted YAML upgrade due issues with CRLF on Windows (#201, [go-yaml/yaml#450](https://github.com/go-yaml/yaml/issues/450)).
-- Allow setting global variables through the CLI (#192).
-
-## 2.5.1 - 2019-04-27
-
-- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues (#114, #190, #200).
-- Upgraded [go-yaml/yaml](https://github.com/go-yaml/yaml) from v2 to v3.
-
-## v2.5.0 - 2019-03-16
-
-- We moved from the taskfile.org domain to the new fancy taskfile.dev domain. While stuff is being redirected, we strongly recommend to everyone that use [this install script](https://taskfile.dev/#/installation?id=install-script) to use the new taskfile.dev domain on scripts from now on.
-- Fixed to the ZSH completion (#182).
-- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) (#180).
-
-## v2.4.0 - 2019-02-21
-
-- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` (#161, #172).
-- Add flag to override the `output` option (#173).
-- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled (#166).
-- Fix file timestamp issue when the file name has spaces (#176).
-- Mitigating path expanding issues on Windows (#170).
-
-## v2.3.0 - 2019-01-02
-
-- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) (#152).
-- Fixed issue with file/directory globing (#153).
-- Added ability to globally set environment variables (#138, #159).
-
-## v2.2.1 - 2018-12-09
-
-- This repository now uses Go Modules (#143). We'll still keep the `vendor` directory in sync for some time, though;
-- Fixing a bug when the Taskfile has no tasks but includes another Taskfile (#150);
-- Fix a bug when calling another task or a dependency in an included Taskfile (#151).
-
-## v2.2.0 - 2018-10-25
-
-- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) (#98)
-  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on #98.
-- Task now have a dedicated documentation site: https://taskfile.org
-  - Thanks to [Docsify](https://docsify.js.org/) for making this pretty easy. To check the source code, just take a look at the [docs](https://github.com/go-task/task/tree/main/docs) directory of this repository. Contributions to the documentation is really appreciated.
-
-## v2.1.1 - 2018-09-17
-
-- Fix suggestion to use `task --init` not being shown anymore (when a `Taskfile.yml` is not found)
-- Fix error when using checksum method and no file exists for a source glob (#131)
-- Fix signal handling when the `--watch` flag is given (#132)
-
-## v2.1.0 - 2018-08-19
-
-- Add a `ignore_error` option to task and command (#123)
-- Add a dry run mode (`--dry` flag) (#126)
-
-## v2.0.3 - 2018-06-24
-
-- Expand environment variables on "dir", "sources" and "generates" (#116)
-- Fix YAML merging syntax (#112)
-- Add ZSH completion (#111)
-- Implement new `output` option. Please check out the [documentation](https://github.com/go-task/task#output-syntax)
-
-## v2.0.2 - 2018-05-01
-
-- Fix merging of YAML anchors (#112)
-
-## v2.0.1 - 2018-03-11
-
-- Fixes panic on `task --list`
-
-## v2.0.0 - 2018-03-08
-
-Version 2.0.0 is here, with a new Taskfile format.
-
-Please, make sure to read the [Taskfile versions](https://github.com/go-task/task/blob/main/TASKFILE_VERSIONS.md) document, since it describes in depth what changed for this version.
-
-- New Taskfile version 2 (#77)
-- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` (#66)
-- Small improvements and fixes
-
-## v1.4.4 - 2017-11-19
-
-- Handle SIGINT and SIGTERM (#75);
-- List: print message with there's no task with description;
-- Expand home dir ("~" symbol) on paths (#74);
-- Add Snap as an installation method;
-- Move examples to its own repo;
-- Watch: also walk on tasks called on on "cmds", and not only on "deps";
-- Print logs to stderr instead of stdout (#68);
-- Remove deprecated `set` keyword;
-- Add checksum based status check, alternative to timestamp based.
-
-## v1.4.3 - 2017-09-07
-
-- Allow assigning variables to tasks at run time via CLI (#33)
-- Added suport for multiline variables from sh (#64)
-- Fixes env: remove square braces and evaluate shell (#62)
-- Watch: change watch library and few fixes and improvements
-- When use watching, cancel and restart long running process on file change (#59 and #60)
-
-## v1.4.2 - 2017-07-30
-
-- Flag to set directory of execution
-- Always echo command if is verbose mode
-- Add silent mode to disable echoing of commands
-- Fixes and improvements of variables (#56)
-
-## v1.4.1 - 2017-07-15
-
-- Allow use of YAML for dynamic variables instead of $ prefix
-  - `VAR: {sh: echo Hello}` instead of `VAR: $echo Hello`
-- Add `--list` (or `-l`) flag to print existing tasks
-- OS specific Taskvars file (e.g. `Taskvars_windows.yml`, `Taskvars_linux.yml`, etc)
-- Consider task up-to-date on equal timestamps (#49)
-- Allow absolute path in generates section (#48)
-- Bugfix: allow templating when calling deps (#42)
-- Fix panic for invalid task in cyclic dep detection
-- Better error output for dynamic variables in Taskvars.yml (#41)
-- Allow template evaluation in parameters
-
-## v1.4.0 - 2017-07-06
-
-- Cache dynamic variables
-- Add verbose mode (`-v` flag)
-- Support to task parameters (overriding vars) (#31) (#32)
-- Print command, also when "set:" is specified (#35)
-- Improve task command help text (#35)
-
-## v1.3.1 - 2017-06-14
-
-- Fix glob not working on commands (#28)
-- Add ExeExt template function
-- Add `--init` flag to create a new Taskfile
-- Add status option to prevent task from running (#27)
-- Allow interpolation on `generates` and `sources` attributes (#26)
-
-## v1.3.0 - 2017-04-24
-
-- Migrate from os/exec.Cmd to a native Go sh/bash interpreter
-  - This is a potentially breaking change if you use Windows.
-  - Now, `cmd` is not used anymore on Windows. Always use Bash-like syntax for your commands, even on Windows.
-- Add "ToSlash" and "FromSlash" to template functions
-- Use functions defined on github.com/Masterminds/sprig
-- Do not redirect stdin while running variables commands
-- Using `context` and `errgroup` packages (this will make other tasks to be cancelled, if one returned an error)
-
-## v1.2.0 - 2017-04-02
-
-- More tests and Travis integration
-- Watch a task (experimental)
-- Possibility to call another task
-- Fix "=" not being reconized in variables/environment variables
-- Tasks can now have a description, and help will print them (#10)
-- Task dependencies now run concurrently
-- Support for a default task (#16)
-
-## v1.1.0 - 2017-03-08
-
-- Support for YAML, TOML and JSON (#1)
-- Support running command in another directory (#4)
-- `--force` or `-f` flag to force execution of task even when it's up-to-date
-- Detection of cyclic dependencies (#5)
-- Support for variables (#6, #9, #14)
-- Operation System specific commands and variables (#13)
-
-## v1.0.0 - 2017-02-28
-
-- Add LICENSE file

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/contributing.md

@@ -1,101 +0,0 @@
----
-slug: /contributing/
-sidebar_position: 11
----
-
-# Contributing
-
-Contributions to Task are very welcome, but we ask that you read this document before submitting a PR.
-
-:::note
-
-This document applies to the core [Task][task] repository _and_ [Task for Visual Studio Code][vscode-task].
-
-:::
-
-## Before you start
-
-- **Check existing work** - Is there an existing PR? Are there issues discussing the feature/change you want to make? Please make sure you consider/address these discussions in your work.
-- **Backwards compatibility** - Will your change break existing Taskfiles? It is much more likely that your change will merged if it backwards compatible. Is there an approach you can take that maintains this compatibility? If not, consider opening an issue first so that API changes can be discussed before you invest your time into a PR.
-- **Experiments** - If there is no way to make your change backward compatible then there is a procedure to introduce breaking changes into minor versions. We call these "\[experiments\]\[experiments\]". If you're intending to work on an experiment, then please read the \[experiments workflow\]\[experiments-workflow\] document carefully and submit a proposal first.
-
-## 1. Setup
-
-- **Go** - Task is written in [Go][go]. We always support the latest two major Go versions, so make sure your version is recent enough.
-- **Node.js** - [Node.js][nodejs] is used to host Task's documentation server and is required if you want to run this server locally. It is also required if you want to contribute to the Visual Studio Code extension.
-- **Yarn** - [Yarn][yarn] is the Node.js package manager used by Task.
-
-## 2. Making changes
-
-- **Code style** - Try to maintain the existing code style where possible. Go code should be formatted by [`gofumpt`][gofumpt] and linted using [`golangci-lint`][golangci-lint]. Any Markdown or TypeScript files should be formatted and linted by [Prettier][prettier]. This style is enforced by our CI to ensure that we have a consistent style across the project. You can use the `task lint` command to lint the code locally and the `task lint:fix` command to automatically fix any issues that are found.
-- **Documentation** - Ensure that you add/update any relevant documentation. See the [updating documentation](#updating-documentation) section below.
-- **Tests** - Ensure that you add/update any relevant tests and that all tests are passing before submitting the PR. See the [writing tests](#writing-tests) section below.
-
-### Running your changes
-
-To run Task with working changes, you can use `go run ./cmd/task`. To run a development build of task against a test Taskfile in `testdata`, you can use `go run ./cmd/task --dir ./testdata/<my_test_dir> <task_name>`.
-
-To run Task for Visual Studio Code, you can open the project in VSCode and hit F5 (or whatever you debug keybind is set to). This will open a new VSCode window with the extension running. Debugging this way is recommended as it will allow you to set breakpoints and step through the code. Otherwise, you can run `task package` which will generate a `.vsix` file that can be used to manually install the extension.
-
-### Updating documentation
-
-Task uses [Docusaurus][docusaurus] to host a documentation server. The code for this is located in the core Task repository. This can be setup and run locally by using `task docs` (requires `nodejs` & `yarn`). All content is written in Markdown and is located in the `docs/docs` directory. All Markdown documents should have an 80 character line wrap limit (enforced by Prettier).
-
-When making a change, consider whether a change to the [Usage Guide](/usage) is necessary. This document contains descriptions and examples of how to use Task features. If you're adding a new feature, try to find an appropriate place to 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 the [Taskfile Styleguide](/styleguide).
-
-If you added a new field, command or flag, ensure that you add it to the [API Reference](/api). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
-
-### Writing tests
-
-A lot of Task's tests are held in the `task_test.go` file in the project root and this is where you'll most likely want to add new ones too. Most of these tests also have a subdirectory in the `testdata` directory where any Taskfiles/data required to run the tests are stored.
-
-When making a changes, consider whether new tests are required. These tests should ensure that the functionality you are adding will continue to work in the future. Existing tests may also need updating if you have changed Task's behavior.
-
-You may also consider adding unit tests for any new functions you have added. The unit tests should follow the Go convention of being location in a file named `*_test.go` in the same package as the code being tested.
-
-## 3. Committing your code
-
-Try to write meaningful commit messages and avoid having too many commits on the PR. Most PRs should likely have a single commit (although for bigger PRs it may be reasonable to split it in a few). Git squash and rebase is your friend!
-
-If you're not sure how to format your commit message, check out [Conventional Commits][conventional-commits]. This style is not enforced, but it is a good way to make your commit messages more readable and consistent.
-
-## 4. Submitting a PR
-
-- **Describe your changes** - Ensure that you provide a comprehensive description of your changes.
-- **Issue/PR links** - Link any previous work such as related issues or PRs. Please describe how your changes differ to/extend this work.
-- **Examples** - Add any examples or screenshots that you think are useful to demonstrate the effect of your changes.
-- **Draft PRs** - If your changes are incomplete, but you would like to discuss them, open the PR as a draft and add a comment to start a discussion. Using comments rather than the PR description allows the description to be updated later while preserving any discussions.
-
-## FAQ
-
-> I want to contribute, where do I start?
-
-Take a look at the list of [open issues for Task][task-open-issues] or [Task for Visual Studio Code][vscode-task-open-issues]. We have a [good first issue][good-first-issue] label for simpler issues that are ideal for first time contributions.
-
-All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](/community).
-
-> I'm stuck, where can I get help?
-
-If you have questions, feel free to ask them in the `#help` forum channel on our [Discord server][discord-server] or open a [Discussion][discussion] on GitHub.
-
----
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[task]: https://github.com/go-task/task
-[vscode-task]: https://github.com/go-task/vscode-task
-[go]: https://go.dev
-[gofumpt]: https://github.com/mvdan/gofumpt
-[golangci-lint]: https://golangci-lint.run
-[prettier]: https://prettier.io
-[nodejs]: https://nodejs.org/en/
-[yarn]: https://yarnpkg.com/
-[docusaurus]: https://docusaurus.io
-[json-schema]: https://github.com/go-task/task/blob/main/docs/static/schema.json
-[task-open-issues]: https://github.com/go-task/task/issues
-[vscode-task-open-issues]: https://github.com/go-task/vscode-task/issues
-[good-first-issue]: https://github.com/go-task/task/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
-[discord-server]: https://discord.gg/6TY36E39UK
-[discussion]: https://github.com/go-task/task/discussions
-[conventional-commits]: https://www.conventionalcommits.org

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/deprecations.md

@@ -1,12 +0,0 @@
----
-slug: /deprecations/
-sidebar_position: 7
----
-
-# Deprecations
-
-As Task evolves, it occasionally outgrows some of its functionality. This can be because they are no longer useful, because another feature has replaced it or because of a change in the way that Task works internally.
-
-When this happens, we mark the functionality as deprecated. This means that it will be removed in a future version of Task. This functionality will continue to work until that time, but we strongly recommend that you do not implement this functionality in new Taskfiles and make a plan to migrate away from it as soon as possible.
-
-You can view a full list of active deprecations in the "Deprecations" section of the sidebar.

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md

@@ -1,25 +0,0 @@
----
-slug: /deprecations/version-2-schema/
----
-
-# Version 2 Schema (#1197)
-
-:::warning
-
-This deprecation breaks the following functionality:
-
-- Any Taskfiles that use the version 2 schema
-- `Taskvar.yml` files
-
-:::
-
-The Taskfile version 2 schema was introduced in March 2018 and replaced by version 3 in August 2019. In May 2023 [we published a deprecation notice][deprecation-notice] for the version 2 schema on the basis that the vast majority of users had already upgraded to version 3 and removing support for version 2 would allow us to tidy up the codebase and focus on new functionality instead.
-
-In December 2023, the final version of Task that supports the version 2 schema ([v3.33.0][v3.33.0]) was published and all legacy code was removed from Task's main branch. To use a more recent version of Task, you will need to ensure that your Taskfile uses the version 3 schema instead. A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][v3.0.0].
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[v3.0.0]: https://github.com/go-task/task/releases/tag/v3.0.0
-[v3.33.0]: https://github.com/go-task/task/releases/tag/v3.33.0
-[deprecation-notice]: https://github.com/go-task/task/issues/1197

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/donate.md

@@ -1,44 +0,0 @@
----
-slug: /donate/
-sidebar_position: 16
----
-
-# Donate
-
-If you find this project useful, you can consider donating by using one of the channels listed below.
-
-This is just a way of saying "thank you", it won't give you any benefits like higher priority on issues or something similar.
-
-Companies who donate at least $50/month will be featured as a "Gold Sponsor" in the website homepage and on the GitHub repository README. Make contact with [@andreynering][] with the logo you want to be shown. Suspect businesses (gambling, casinos, etc) won't be allowed, though.
-
-## GitHub Sponsors
-
-The preferred way to donate to the maintainers is via GitHub Sponsors. Just use the following links to do your donation. We suggest a 50/50 split to each maintainer of the total amount you plan to donate to the project.
-
-- [@andreynering](https://github.com/sponsors/andreynering)
-- [@pd93](https://github.com/sponsors/pd93)
-
-## Open Collective
-
-If you prefer [Open Collective](https://opencollective.com/task) you can donate by using these links:
-
-- [$2 per month](https://opencollective.com/task/contribute/backer-4034/checkout)
-- [$5 per month](https://opencollective.com/task/contribute/supporter-8404/checkout)
-- [$20 per month](https://opencollective.com/task/contribute/sponsor-4035/checkout)
-- [$50 per month](https://opencollective.com/task/contribute/sponsor-28775/checkout)
-- [Custom value - One-time donation option supported](https://opencollective.com/task/donate)
-
-## PayPal
-
-You can donate to [@andreynering][] via PayPal as well:
-
-- [Any value - One-time donation](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=GSVDU63RKG45A&currency_code=USD&source=url)
-
-## PIX (Brazil only)
-
-And if you're Brazilian, you can also donate to [@andreynering][] via PIX by [using this QR Code](/img/pix.png).
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[@andreynering]: https://github.com/andreynering

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/any_variables.md

@@ -1,206 +0,0 @@
----
-slug: /experiments/any-variables/
----
-
-# Any Variables (#1415)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any
-time_. We strongly recommend that you do not use these features in a production
-environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- Dynamically defined variables (using the `sh` keyword)
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable:
-`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
-][enabling-experiments] for more information.
-
-:::
-
-Currently, Task only supports string variables. This experiment allows you to
-specify and use the following variable types:
-
-- `string`
-- `bool`
-- `int`
-- `float`
-- `array`
-- `map`
-
-This allows you to have a lot more flexibility in how you use variables in
-Task's templating engine. For example:
-
-Evaluating booleans:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      BOOL: false
-    cmds:
-      - '{{if .BOOL}}echo foo{{end}}'
-```
-
-Arithmetic:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      INT: 10
-      FLOAT: 3.14159
-    cmds:
-      - 'echo {{add .INT .FLOAT}}'
-```
-
-Ranging:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      ARRAY: [1, 2, 3]
-    cmds:
-      - 'echo {{range .ARRAY}}{{.}}{{end}}'
-```
-
-There are many more templating functions which can be used with the new types of
-variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
-
-## Looping over variables
-
-Previously, you would have to use a delimiter separated string to loop over an
-arbitrary list of items in a variable and split them by using the `split` subkey
-to specify the delimiter:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: 'foo,bar,baz'
-    cmds:
-      - for:
-          var: LIST
-          split: ','
-        cmd: echo {{.ITEM}}
-```
-
-Because this experiment adds support for "collection-type" variables, the `for`
-keyword has been updated to support looping over arrays directly:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: [foo, bar, baz]
-    cmds:
-      - for:
-          var: LIST
-        cmd: echo {{.ITEM}}
-```
-
-This also works for maps. When looping over a map we also make an additional
-`{{.KEY}}` variable availabe that holds the string value of the map key.
-Remember that maps are unordered, so the order in which the items are looped
-over is random:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      MAP:
-        KEY_1:
-          SUBKEY: sub_value_1
-        KEY_2:
-          SUBKEY: sub_value_2
-        KEY_3:
-          SUBKEY: sub_value_3
-    cmds:
-      - for:
-          var: MAP
-        cmd: echo {{.KEY}} {{.ITEM.SUBKEY}}
-```
-
-String splitting is still supported and remember that for simple cases, you have
-always been able to loop over an array without using variables at all:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    cmds:
-      - for: [foo, bar, baz]
-        cmd: echo {{.ITEM}}
-```
-
-## Migration
-
-Taskfiles with dynamically defined variables via the `sh` subkey will no longer
-work with this experiment enabled. In order to keep using dynamically defined
-variables, you will need to migrate your Taskfile to use the new syntax.
-
-Previously, you might have defined a dynamic variable like this:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR:
-        sh: 'echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-With this experiment enabled, you will need to remove the `sh` subkey and define
-your command as a string that begins with a `$`. This will instruct Task to
-interpret the string as a command instead of a literal value and the variable
-will be populated with the output of the command. For example:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR: '$echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-If your current Taskfile contains a string variable that begins with a `$`, you
-will now need to escape the `$` with a backslash (`\`) to stop Task from
-executing it as a command.
-
-<!-- prettier-ignore-start -->
-
-[enabling-experiments]: /experiments/#enabling-experiments
-
-[slim-sprig]: https://go-task.github.io/slim-sprig/
-
-<!-- prettier-ignore-end -->

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/any_variables.mdx

@@ -1,162 +0,0 @@
----
-slug: /experiments/any-variables/
----
-
-# Any Variables
-
--   Issue: #1415
--   Environment variable: `TASK_X_ANY_VARIABLES=1`
--   Breaks:
-    -   Dynamically defined variables (using the `sh` keyword)
-
-Currently, Task only supports string variables. This experiment allows you to
-specify and use the following variable types:
-
--   `string`
--   `bool`
--   `int`
--   `float`
--   `array`
--   `map`
-
-This allows you to have a lot more flexibility in how you use variables in
-Task's templating engine. For example:
-
-Evaluating booleans:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      BOOL: false
-    cmds:
-      - '{{if .BOOL}}echo foo{{end}}'
-```
-
-Arithmetic:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      INT: 10
-      FLOAT: 3.14159
-    cmds:
-      - 'echo {{add .INT .FLOAT}}'
-```
-
-Ranging:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      ARRAY: [1, 2, 3]
-    cmds:
-      - 'echo {{range .ARRAY}}{{.}}{{end}}'
-```
-
-There are many more templating functions which can be used with the new types of
-variables. For a full list, see the
-[slim-sprig][slim-sprig] documentation.
-
-## Looping over variables
-
-Previously, you would have to use a delimiter separated string to loop over an
-arbitrary list of items in a variable and split them by using the `split` subkey
-to specify the delimiter:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: 'foo,bar,baz'
-    cmds:
-      - for:
-          var: LIST
-          split: ','
-        cmd: echo {{.ITEM}}
-```
-
-Because this experiment adds support for array variables, the `for` keyword has
-been updated to support looping over arrays directly:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: [foo, bar, baz]
-    cmds:
-      - for:
-          var: LIST
-        cmd: echo {{.ITEM}}
-```
-
-String splitting is still supported and remember that for simple cases, you have
-always been able to loop over an array without using variables at all:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    cmds:
-      - for: [foo, bar, baz]
-        cmd: echo {{.ITEM}}
-```
-
-## Migration
-
-Taskfiles with dynamically defined variables via the `sh` subkey will no longer
-work with this experiment enabled. In order to keep using dynamically defined
-variables, you will need to migrate your Taskfile to use the new syntax.
-
-Previously, you might have defined a dynamic variable like this:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR:
-        sh: 'echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-With this experiment enabled, you will need to remove the `sh` subkey and define
-your command as a string that begins with a `$`. This will instruct Task to
-interpret the string as a command instead of a literal value and the variable
-will be populated with the output of the command. For example:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR: '$echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-If your current Taskfile contains a string variable that begins with a `$`, you
-will now need to escape the `$` with a backslash (`\`) to stop Task from
-executing it as a command.
-
-<!-- prettier-ignore-start -->
-
-[slim-sprig]: https://go-task.github.io/slim-sprig/
-
-<!-- prettier-ignore-end -->

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/experiments.md

@@ -1,79 +0,0 @@
----
-slug: /experiments/
-sidebar_position: 6
----
-
-# Experiments
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-In order to allow Task to evolve quickly, we roll out breaking changes to minor versions behind experimental flags. This allows us to gather feedback on breaking changes before committing to a major release. This document describes the current set of experimental features and their status in the [workflow](#workflow).
-
-You can view a full list of active experiments in the "Experiments" section of the sidebar.
-
-## Enabling Experiments
-
-You can enable an experimental feature by doing one of the following:
-
-1. Using the relevant environment variable in front of a task command. For example, `TASK_X_{FEATURE}=1 task {my-task}`. This is intended for one-off invocations of Task to test out experimental features.
-1. Using the relevant environment variable in your "dotfiles" (e.g. `.bashrc`, `.zshrc` etc.). This is intended for permanently enabling experimental features in your environment.
-1. Creating a `.env` file in the same directory as your root Taskfile that contains the relevant environment variables. This allows you to enable an experimental feature at a project level. For example:
-
-```shell title=".env"
-TASK_X_FEATURE=1
-```
-
-## Current Experimental Features and Deprecations
-
-Each section below details an experiment or deprecation and explains what the flags/environment variables to enable the experiment are and how the feature's behavior will change. It will also explain what you need to do to migrate any existing Taskfiles to the new behavior.
-
-## Workflow
-
-Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
-
-The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
-
-### 1. Proposal
-
-All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
-
-### 2. Draft
-
-Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
-
-:::note
-
-During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
-
-:::
-
-### 3. Candidate
-
-Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
-
-### 4. Stable
-
-Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
-
-### 5. Released
-
-When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
-
-### Abandoned / Superseded
-
-If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
-[draft]: https://img.shields.io/badge/experiment:%20draft-purple
-[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
-[stable]: https://img.shields.io/badge/experiment:%20stable-purple
-[released]: https://img.shields.io/badge/experiment:%20released-purple
-[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
-[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/gentle_force.md

@@ -1,36 +0,0 @@
----
-slug: /experiments/gentle-force/
----
-
-# Gentle Force (#1200)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- The `--force` flag
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_FORCE=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
-
-This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
-
-If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md

@@ -1,66 +0,0 @@
----
-slug: /experiments/remote-taskfiles/
----
-
-# Remote Taskfiles (#1317)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-This experiment allows you to specify a remote Taskfile URL when including a Taskfile. For example:
-
-```yaml
-version: '3'
-
-includes:
-  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
-```
-
-This works exactly the same way that including a local file does. Any tasks in the remote Taskfile will be available to run from your main Taskfile via the namespace `my-remote-namespace`. For example, if the remote file contains the following:
-
-```yaml
-version: '3'
-
-tasks:
-  hello:
-    silent: true
-    cmds:
-      - echo "Hello from the remote Taskfile!"
-```
-
-and you run `task my-remote-namespace:hello`, it will print the text: "Hello from the remote Taskfile!" to your console.
-
-## Security
-
-Running commands from sources that you do not control is always a potential security risk. For this reason, we have added some checks when using remote Taskfiles:
-
-1. When running a task from a remote Taskfile for the first time, Task will print a warning to the console asking you to check that you are sure that you trust the source of the Taskfile. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the remote Taskfile will run and further calls to the remote Taskfile will not prompt you again.
-2. Whenever you run a remote Taskfile, Task will create and store a checksum of the file that you are running. If the checksum changes, then Task will print another warning to the console to inform you that the contents of the remote file has changed. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the checksum will be updated and the remote Taskfile will run.
-
-Sometimes you need to run Task in an environment that does not have an interactive terminal, so you are not able to accept a prompt. In these cases you are able to tell task to accept these prompts automatically by using the `--yes` flag. Before enabling this flag, you should:
-
-1. Be sure that you trust the source and contents of the remote Taskfile.
-2. Consider using a pinned version of the remote Taskfile (e.g. A link containing a commit hash) to prevent Task from automatically accepting a prompt that says a remote Taskfile has changed.
-
-Task currently supports both `http` and `https` URLs. However, the `http` requests will not execute by default unless you run the task with the `--insecure` flag. This is to protect you from accidentally running a remote Taskfile that is hosted on and unencrypted connection. Sources that are not protected by TLS are vulnerable to [man-in-the-middle attacks][man-in-the-middle-attacks] and should be avoided unless you know what you are doing.
-
-## Caching & Running Offline
-
-Whenever you run a remote Taskfile, the latest copy will be downloaded from the internet and cached locally. If for whatever reason, you lose access to the internet, you will still be able to run your tasks by specifying the `--offline` flag. This will tell Task to use the latest cached version of the file instead of trying to download it. You are able to use the `--download` flag to update the cached version of the remote files without running any tasks.
-
-By default, Task will timeout requests to download remote files after 10 seconds and look for a cached copy instead. This timeout can be configured by setting the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will set the timeout to 5 seconds.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments
-[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/template.md

@@ -1,39 +0,0 @@
----
-#This is a template for an experiments documentation
-#Copy this page and fill in the details as necessary
-title: '--- Template ---'
-sidebar_position: -1 #Always push to the top
-draft: true #Hide in production
----
-
-# \{Name of Experiment\} (#\{Issue\})
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- \{list any existing functionality that will be broken by this experiment\}
-- \{if there are no breaking changes, remove this admonition\}
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_{feature}=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-\{Short description of the feature\}
-
-\{Short explanation of how users should migrate to the new behavior\}
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/workflow.md

@@ -1,50 +0,0 @@
----
-slug: /experiments/workflow/
----
-
-# Workflow
-
-Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
-
-The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
-
-## 1. Proposal
-
-All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
-
-## 2. Draft
-
-Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
-
-:::note
-
-During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
-
-:::
-
-## 3. Candidate
-
-Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
-
-## 4. Stable
-
-Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
-
-## 5. Released
-
-When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
-
-## Abandoned / Superseded
-
-If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
-[draft]: https://img.shields.io/badge/experiment:%20draft-purple
-[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
-[stable]: https://img.shields.io/badge/experiment:%20stable-purple
-[released]: https://img.shields.io/badge/experiment:%20released-purple
-[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
-[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/faq.md

@@ -1,89 +0,0 @@
----
-slug: /faq/
-sidebar_position: 15
----
-
-# FAQ
-
-This page contains a list of frequently asked questions about Task.
-
-## Why won't my task update my shell environment?
-
-This is a limitation of how shells work. Task runs as a subprocess of your current shell, so it can't change the environment of the shell that started it. This limitation is shared by other task runners and build tools too.
-
-A common way to work around this is to create a task that will generate output that can be parsed by your shell. For example, to set an environment variable on your shell you can write a task like this:
-
-```yaml
-my-shell-env:
-  cmds:
-    - echo "export FOO=foo"
-    - echo "export BAR=bar"
-```
-
-Now run `eval $(task my-shell-env)` and the variables `$FOO` and `$BAR` will be available in your shell.
-
-## I can't reuse my shell in a task's commands
-
-Task runs each command as a separate shell process, so something you do in one command won't effect any future commands. For example, this won't work:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - a=foo
-      - echo $a
-      # outputs ""
-```
-
-To work around this you can either use a multiline command:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - |
-        a=foo
-        echo $a
-      # outputs "foo"
-```
-
-Or for more complex multi-line commands it is recommended to move your code into a separate file and call that instead:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - ./foo-printer.bash
-```
-
-```bash
-#!/bin/bash
-a=foo
-echo $a
-```
-
-## 'x' builtin command doesn't work on Windows
-
-The default shell on Windows (`cmd` and `powershell`) do not have commands like `rm` and `cp` available as builtins. This means that these commands won't work. If you want to make your Taskfile fully cross-platform, you'll need to work around this limitation using one of the following methods:
-
-- Use the `{{OS}}` function to run an OS-specific script.
-- Use something like `{{if eq OS "windows"}}powershell {{end}}<my_cmd>` to detect windows and run the command in Powershell directly.
-- Use a shell on Windows that supports these commands as builtins, such as [Git Bash][git-bash] or [WSL][wsl].
-
-We want to make improvements to this part of Task and the issues below track this work. Constructive comments and contributions are very welcome!
-
-- #197
-- [mvdan/sh#93](https://github.com/mvdan/sh/issues/93)
-- [mvdan/sh#97](https://github.com/mvdan/sh/issues/97)
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[git-bash]: https://gitforwindows.org/
-[wsl]: https://learn.microsoft.com/en-us/windows/wsl/install

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/installation.md

@@ -1,266 +0,0 @@
----
-slug: /installation/
-sidebar_position: 2
----
-
-# Installation
-
-Task offers many installation methods. Check out the available methods below.
-
-## Package Managers
-
-### Homebrew
-
-If you're on macOS or Linux and have [Homebrew][homebrew] installed, getting Task is as simple as running:
-
-```bash
-brew install go-task/tap/go-task
-```
-
-The above Formula is [maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb).
-
-Recently, Task was also made available [on the official Homebrew repository](https://formulae.brew.sh/formula/go-task), so you also have that option if you prefer:
-
-```bash
-brew install go-task
-```
-
-### Tea
-
-If you're on macOS or Linux and have [tea][tea] installed, getting Task is as simple as running:
-
-```bash
-tea task
-```
-
-or, if you have tea’s magic enabled:
-
-```bash
-task
-```
-This installation method is community owned. After a new release of Task, they are automatically released by tea in a minimum of time.
-
-### Snap
-
-Task is available in [Snapcraft][snapcraft], but keep in mind that your Linux distribution should allow classic confinement for Snaps to Task work right:
-
-```bash
-sudo snap install task --classic
-```
-
-### Chocolatey
-
-If you're on Windows and have [Chocolatey][choco] installed, getting Task is as simple as running:
-
-```bash
-choco install go-task
-```
-
-This installation method is community owned.
-
-### Scoop
-
-If you're on Windows and have [Scoop][scoop] installed, getting Task is as simple as running:
-
-```cmd
-scoop install task
-```
-
-This installation method is community owned. After a new release of Task, it may take some time until it's available on Scoop.
-
-### AUR
-
-If you're on Arch Linux you can install Task from [AUR](https://aur.archlinux.org/packages/go-task-bin) using your favorite package manager such as `yay`, `pacaur` or `yaourt`:
-
-```cmd
-yay -S go-task-bin
-```
-
-Alternatively, there's [this package](https://aur.archlinux.org/packages/go-task) which installs from the source code instead of downloading the binary from the [releases page](https://github.com/go-task/task/releases):
-
-```cmd
-yay -S go-task
-```
-
-This installation method is community owned.
-
-### Fedora
-
-If you're on Fedora Linux you can install Task from the official [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/) repository using `dnf`:
-
-```cmd
-sudo dnf install go-task
-```
-
-This installation method is community owned. After a new release of Task, it may take some time until it's available in [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/).
-
-### Nix
-
-If you're on NixOS or have Nix installed you can install Task from [nixpkgs](https://github.com/NixOS/nixpkgs):
-
-```cmd
-nix-env -iA nixpkgs.go-task
-```
-
-This installation method is community owned. After a new release of Task, it may take some time until it's available in [nixpkgs](https://github.com/NixOS/nixpkgs).
-
-### npm
-
-You can also use Node and npm to install Task by installing [this package](https://www.npmjs.com/package/@go-task/cli).
-
-```bash
-npm install -g @go-task/cli
-```
-
-### Winget
-
-If you are using Windows and installed the [winget](https://github.com/microsoft/winget-cli) package management tool, you can install Task from [winget-pkgs](https://github.com/microsoft/winget-pkgs).
-
-```bash
-winget install Task.Task
-```
-
-## Get The Binary
-
-### Binary
-
-You can download the binary from the [releases page on GitHub][releases] and add to your `$PATH`.
-
-DEB and RPM packages are also available.
-
-The `task_checksums.txt` file contains the SHA-256 checksum for each file.
-
-### Install Script
-
-We also have an [install script][installscript] which is very useful in scenarios like CI. Many thanks to [GoDownloader][godownloader] for enabling the easy generation of this script.
-
-By default, it installs on the `./bin` directory relative to the working directory:
-
-```bash
-sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d
-```
-
-It is possible to override the installation directory with the `-b` parameter. On Linux, common choices are `~/.local/bin` and `~/bin` to install for the current user or `/usr/local/bin` to install for all users:
-
-```bash
-sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
-```
-
-:::caution
-
-On macOS and Windows, `~/.local/bin` and `~/bin` are not added to `$PATH` by default.
-
-:::
-
-### GitHub Actions
-
-If you want to install Task in GitHub Actions you can try using [this action](https://github.com/arduino/setup-task) by the Arduino team:
-
-```yaml
-- name: Install Task
-  uses: arduino/setup-task@v1
-  with:
-    version: 3.x
-    repo-token: ${{ secrets.GITHUB_TOKEN }}
-```
-
-This installation method is community owned.
-
-## Build From Source
-
-### Go Modules
-
-Ensure that you have a supported version of [Go][go] properly installed and setup. You can find the minimum required version of Go in the [go.mod](https://github.com/go-task/task/blob/main/go.mod#L3) file.
-
-You can then install the latest release globally by running:
-
-```bash
-go install github.com/go-task/task/v3/cmd/task@latest
-```
-
-Or you can install into another directory:
-
-```bash
-env GOBIN=/bin go install github.com/go-task/task/v3/cmd/task@latest
-```
-
-:::tip
-
-For CI environments we recommend using the [install script](#install-script) instead, which is faster and more stable, since it'll just download the latest released binary.
-
-:::
-
-## Setup completions
-
-Download the autocompletion file corresponding to your shell.
-
-[All completions are available on the Task repository](https://github.com/go-task/task/tree/main/completion).
-
-### Bash
-
-First, ensure that you installed bash-completion using your package manager.
-
-Make the completion file executable:
-
-```
-chmod +x path/to/task.bash
-```
-
-After, add this to your `~/.bash_profile`:
-
-```shell
-source path/to/task.bash
-```
-
-### ZSH
-
-Put the `_task` file somewhere in your `$FPATH`:
-
-```shell
-mv path/to/_task /usr/local/share/zsh/site-functions/_task
-```
-
-Ensure that the following is present in your `~/.zshrc`:
-
-```shell
-autoload -U compinit
-compinit -i
-```
-
-ZSH version 5.7 or later is recommended.
-
-### Fish
-
-Move the `task.fish` completion script:
-
-```shell
-mv path/to/task.fish ~/.config/fish/completions/task.fish
-```
-
-### PowerShell
-
-Open your profile script with:
-
-```
-mkdir -Path (Split-Path -Parent $profile) -ErrorAction SilentlyContinue
-notepad $profile
-```
-
-Add the line and save the file:
-
-```shell
-Invoke-Expression -Command path/to/task.ps1
-```
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[go]: https://golang.org/
-[snapcraft]: https://snapcraft.io/task
-[homebrew]: https://brew.sh/
-[installscript]: https://github.com/go-task/task/blob/main/install-task.sh
-[releases]: https://github.com/go-task/task/releases
-[godownloader]: https://github.com/goreleaser/godownloader
-[choco]: https://chocolatey.org/
-[scoop]: https://scoop.sh/
-[tea]: https://tea.xyz/

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/integrations.md

@@ -1,62 +0,0 @@
----
-slug: /integrations/
-sidebar_position: 8
----
-
-# Integrations
-
-## Visual Studio Code Extension
-
-Task has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task). El código de ese proyecto puede ser encontrado [aquí](https://github.com/go-task/vscode-task). Para usar la extensión es necesario tener instalada la versión v3.23.0+ de Task.
-
-La extensión proporciona las siguientes funcionalidades (y más...):
-
-- View tasks in the sidebar.
-- Ejecuta tareas desde la barra lateral y la paleta de comandos.
-- Go to definition from the sidebar and command palette.
-- Run last task command.
-- Multi-root workspace support.
-- Initialize a Taskfile in the current workspace.
-
-To get autocompletion and validation for your Taskfile, see the [Schema](#schema) section below.
-
-![Task for Visual Studio Code](https://github.com/go-task/vscode-task/blob/main/res/preview.png?raw=true)
-
-## Schema
-
-This was initially created by @KROSF in [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and is now officially maintained in [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json) and made available at https://taskfile.dev/schema.json. This schema can be used to validate Taskfiles and provide autocompletion in many code editors:
-
-### Visual Studio Code
-
-To integrate the schema into VS Code, you need to install the [YAML extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) by Red Hat. Any `Taskfile.yml` in your project should automatically be detected and validation/autocompletion should work. If this doesn't work or you want to manually configure it for files with a different name, you can add the following to your `settings.json`:
-
-```json
-// settings.json
-{
-  "yaml.schemas": {
-    "https://taskfile.dev/schema.json": [
-      "**/Taskfile.yml",
-      "./path/to/any/other/taskfile.yml"
-    ]
-  }
-}
-```
-
-You can also configure the schema directly inside of a Taskfile by adding the following comment to the top of the file:
-
-```yaml
-# yaml-language-server: $schema=https://taskfile.dev/schema.json
-version: '3'
-```
-
-You can find more information on this in the [YAML language server project](https://github.com/redhat-developer/yaml-language-server).
-
-## Community Integrations
-
-In addition to our official integrations, there is an amazing community of developers who have created their own integrations for Task:
-
-- [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile) [[source](https://github.com/biozz/sublime-taskfile)] by @biozz
-- [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile) [[source](https://github.com/lechuckroh/task-intellij-plugin)] by @lechuckroh
-- [mk](https://github.com/pycontribs/mk) command line tool recognizes Taskfiles natively.
-
-If you have made something that integrates with Task, please feel free to open a PR to add it to this list.

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/intro.md

@@ -1,49 +0,0 @@
----
-slug: /
-sidebar_position: 1
-title: Home
----
-
-# Task
-
-<div align="center">
-  <img id="logo" src="img/logo.svg" height="250px" width="250px" />
-</div>
-
-Task is a task runner / build tool that aims to be simpler and easier to use than, for example, [GNU Make][make].
-
-Since it's written in [Go][go], Task is just a single binary and has no other dependencies, which means you don't need to mess with any complicated install setups just to use a build tool.
-
-Once [installed](/installation), you just need to describe your build tasks using a simple [YAML][yaml] schema in a file called `Taskfile.yml`:
-
-```yaml title="Taskfile.yml"
-version: '3'
-
-tasks:
-  hello:
-    cmds:
-      - echo 'Hello World from Task!'
-    silent: true
-```
-
-And call it by running `task hello` from your terminal.
-
-The above example is just the start, you can take a look at the [usage](/usage) guide to check the full schema documentation and Task features.
-
-## Features
-
-- [Easy installation](/installation): just download a single binary, add to `$PATH` and you're done! Or you can also install using [Homebrew][homebrew], [Snapcraft][snapcraft], or [Scoop][scoop] if you want.
-- Available on CIs: by adding [this simple command](/installation#install-script) to install on your CI script and you're ready to use Task as part of your CI pipeline;
-- Truly cross-platform: while most build tools only work well on Linux or macOS, Task also supports Windows thanks to [this shell interpreter for Go][sh].
-- Great for code generation: you can easily [prevent a task from running](/usage#prevent-unnecessary-work) if a given set of files haven't changed since last run (based either on its timestamp or content).
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[make]: https://www.gnu.org/software/make/
-[go]: https://go.dev/
-[yaml]: http://yaml.org/
-[homebrew]: https://brew.sh/
-[snapcraft]: https://snapcraft.io/
-[scoop]: https://scoop.sh/
-[sh]: https://github.com/mvdan/sh

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/releasing.md

@@ -1,50 +0,0 @@
----
-slug: /releasing/
-sidebar_position: 13
----
-
-# Releasing
-
-The release process of Task is done with the help of [GoReleaser][goreleaser]. You can test the release process locally by calling the `test-release` task of the Taskfile.
-
-[GitHub Actions](https://github.com/go-task/task/actions) should release artifacts automatically when a new Git tag is pushed to `main` branch (raw executables and DEB and RPM packages).
-
-Since v3.15.0, raw executables can also be reproduced and verified locally by checking out a specific tag and calling `goreleaser build`, using the Go version defined in the above GitHub Actions.
-
-# Homebrew
-
-Goreleaser will automatically push a new commit to the [Formula/go-task.rb][gotaskrb] file in the [Homebrew tap][homebrewtap] repository to release the new version.
-
-# npm
-
-To release to npm update the version in the [`package.json`][packagejson] file and then run `task npm:publish` to push it.
-
-# Snapcraft
-
-The [snap package][snappackage] requires to manual steps to release a new version:
-
-- Updating the current version on [snapcraft.yaml][snapcraftyaml].
-- Moving both `amd64`, `armhf` and `arm64` new artifacts to the stable channel on the [Snapcraft dashboard][snapcraftdashboard].
-
-# winget
-
-winget also requires manual steps to be completed. By running `task goreleaser:test` locally, manifest files will be generated on `dist/winget/manifests/t/Task/Task/v{version}`. [Upload the manifest directory into this fork](https://github.com/go-task/winget-pkgs/tree/master/manifests/t/Task/Task) and open a pull request into [this repository](https://github.com/microsoft/winget-pkgs).
-
-# Scoop
-
-Scoop is a command-line package manager for the Windows operating system. Scoop package manifests are maintained by the community. Scoop owners usually take care of updating versions there by editing [this file](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json). If you think its Task version is outdated, open an issue to let us know.
-
-# Nix
-
-Nix is a community owned installation method. Nix package maintainers usually take care of updating versions there by editing [this file](https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/tools/go-task/default.nix). If you think its Task version is outdated, open an issue to let us know.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[goreleaser]: https://goreleaser.com/
-[homebrewtap]: https://github.com/go-task/homebrew-tap
-[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb
-[packagejson]: https://github.com/go-task/task/blob/main/package.json#L3
-[snappackage]: https://github.com/go-task/snap
-[snapcraftyaml]: https://github.com/go-task/snap/blob/main/snap/snapcraft.yaml#L2
-[snapcraftdashboard]: https://snapcraft.io/task/releases

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/taskfile_versions.md

@@ -1,240 +0,0 @@
----
-slug: /taskfile-versions/
-sidebar_position: 5
----
-
-# Taskfile Versions
-
-The Taskfile syntax and features changed with time. This document explains what changed on each version and how to upgrade your Taskfile.
-
-## What the Taskfile version mean
-
-The Taskfile version follows the Task version. E.g. the change to Taskfile version `2` means that Task `v2.0.0` should be release to support it.
-
-The `version:` key on Taskfile accepts a semver string, so either `2`, `2.0` or `2.0.0` is accepted. If you choose to use `2.0` Task will not enable future `2.1` features, but if you choose to use `2`, then any `2.x.x` features will be available, but not `3.0.0+`.
-
-## Version 3 ![latest](https://img.shields.io/badge/latest-brightgreen)
-
-These are some major changes done on `v3`:
-
-- Task's output will now be colored
-- Added support for `.env` like files
-- Added `label:` setting to task so one can override how the task name appear in the logs
-- A global `method:` was added to allow setting the default method, and Task's default changed to `checksum`
-- Two magic variables were added when using `status:`: `CHECKSUM` and `TIMESTAMP` which contains, respectively, the XXH3 checksum and greatest modification timestamp of the files listed on `sources:`
-- Also, the `TASK` variable is always available with the current task name
-- CLI variables are always treated as global variables
-- Added `dir:` option to `includes` to allow choosing on which directory an included Taskfile will run:
-
-```yaml
-includes:
-  docs:
-    taskfile: ./docs
-    dir: ./docs
-```
-
-- Implemented short task syntax. All below syntaxes are equivalent:
-
-```yaml
-version: '3'
-
-tasks:
-  print:
-    cmds:
-      - echo "Hello, World!"
-```
-
-```yaml
-version: '3'
-
-tasks:
-  print:
-    - echo "Hello, World!"
-```
-
-```yaml
-version: '3'
-
-tasks:
-  print: echo "Hello, World!"
-```
-
-- There was a major refactor on how variables are handled. They're now easier to understand. The `expansions:` setting was removed as it became unnecessary. This is the order in which Task will process variables, each level can see the variables set by the previous one and override those.
-  - Environment variables
-  - Global + CLI variables
-  - Call variables
-  - Task variables
-
-## Version 2.6
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.6 comes with `preconditions` stanza in tasks.
-
-```yaml
-version: '2'
-
-tasks:
-  upload_environment:
-    preconditions:
-      - test -f .env
-    cmds:
-      - aws s3 cp .env s3://myenvironment
-```
-
-Please check the [documentation][includes]
-
-## Version 2.2
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.2 comes with a global `includes` options to include other Taskfiles:
-
-```yaml
-version: '2'
-
-includes:
-  docs: ./documentation # will look for ./documentation/Taskfile.yml
-  docker: ./DockerTasks.yml
-```
-
-## Version 2.1
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
-
-:::
-
-Version 2.1 includes a global `output` option, to allow having more control over how commands output are printed to the console (see [documentation][output] for more info):
-
-```yaml
-version: '2'
-
-output: prefixed
-
-tasks:
-  server:
-    cmds:
-      - go run main.go
-  prefix: server
-```
-
-From this version it's also possible to ignore errors of a command or task (check documentation [here][ignore_errors]):
-
-```yaml
-version: '2'
-
-tasks:
-  example-1:
-    cmds:
-      - cmd: exit 1
-        ignore_error: true
-      - echo "This will be print"
-
-  example-2:
-    cmds:
-      - exit 1
-      - echo "This will be print"
-    ignore_error: true
-```
-
-## Version 2.0
-
-:::caution
-
-v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
-
-:::
-
-At version 2, we introduced the `version:` key, to allow us to evolve Task with new features without breaking existing Taskfiles. The new syntax is as follows:
-
-```yaml
-version: '2'
-
-tasks:
-  echo:
-    cmds:
-      - echo "Hello, World!"
-```
-
-Version 2 allows you to write global variables directly in the Taskfile, if you don't want to create a `Taskvars.yml`:
-
-```yaml
-version: '2'
-
-vars:
-  GREETING: Hello, World!
-
-tasks:
-  greet:
-    cmds:
-      - echo "{{.GREETING}}"
-```
-
-The variable priority order changed to the following:
-
-1. Task variables
-2. Call variables
-3. Taskfile variables
-4. Taskvars file variables
-5. Environment variables
-
-A new global option was added to configure the number of variables expansions (which default to 2):
-
-```yaml
-version: '2'
-
-expansions: 3
-
-vars:
-  FOO: foo
-  BAR: bar
-  BAZ: baz
-  FOOBAR: '{{.FOO}}{{.BAR}}'
-  FOOBARBAZ: '{{.FOOBAR}}{{.BAZ}}'
-
-tasks:
-  default:
-    cmds:
-      - echo "{{.FOOBARBAZ}}"
-```
-
-## Version 1
-
-:::caution
-
-v1 schema support was removed in Task >= v3.0.0.
-
-:::
-
-In the first version of the `Taskfile`, the `version:` key was not available, because the tasks was in the root of the YAML document. Like this:
-
-```yaml
-echo:
-  cmds:
-    - echo "Hello, World!"
-```
-
-The variable priority order was also different:
-
-1. Call variables
-2. Environment
-3. Task variables
-4. `Taskvars.yml` variables
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[deprecate-version-2-schema]: /deprecations/version-2-schema/
-[output]: /usage#output-syntax
-[ignore_errors]: /usage#ignore-errors
-[includes]: /usage#including-other-taskfiles

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/translate.md

@@ -1,18 +0,0 @@
----
-slug: /translate/
-sidebar_position: 12
----
-
-# Translate
-
-Want to help us translate this documentation? In this document we explain how.
-
-Do NOT edit translated markdown files directly on the GitHub repository! We use [Crowdin][crowdin] to allow contributors on work on translations. The repository is periodically updated with progress from Crowdin.
-
-If you want to have access to the Crowdin project to be able to suggest translations, please ask for access on the [#translations channel on our Discord server][discord]. If a given language is not being shown to Crowdin yet, just ask and we can configure it.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[crowdin]: https://crowdin.com/project/taskfile
-[discord]: https://discord.gg/6TY36E39UK

docs/i18n/es-ES/docusaurus-theme-classic/footer.json

@@ -1,46 +0,0 @@
-{
-  "link.title.Pages": {
-    "message": "Páginas",
-    "description": "The title of the footer links column with title=Pages in the footer"
-  },
-  "link.title.Community": {
-    "message": "Comunidad",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.Translations": {
-    "message": "Traducciones",
-    "description": "The title of the footer links column with title=Translations in the footer"
-  },
-  "link.item.label.Installation": {
-    "message": "Instalación",
-    "description": "The label of footer link with label=Installation linking to /installation/"
-  },
-  "link.item.label.Usage": {
-    "message": "Uso",
-    "description": "The label of footer link with label=Usage linking to /usage/"
-  },
-  "link.item.label.Donate": {
-    "message": "Donar",
-    "description": "The label of footer link with label=Donate linking to /donate/"
-  },
-  "link.item.label.GitHub": {
-    "message": "GitHub",
-    "description": "The label of footer link with label=GitHub linking to https://github.com/go-task/task"
-  },
-  "link.item.label.Twitter": {
-    "message": "Twitter",
-    "description": "The label of footer link with label=Twitter linking to https://twitter.com/taskfiledev"
-  },
-  "link.item.label.Mastodon": {
-    "message": "Mastodon",
-    "description": "The label of footer link with label=Mastodon linking to https://fosstodon.org/@task"
-  },
-  "link.item.label.Discord": {
-    "message": "Discord",
-    "description": "The label of footer link with label=Discord linking to https://discord.gg/6TY36E39UK"
-  },
-  "link.item.label.OpenCollective": {
-    "message": "OpenCollective",
-    "description": "The label of footer link with label=OpenCollective linking to https://opencollective.com/task"
-  }
-}

docs/i18n/es-ES/docusaurus-theme-classic/navbar.json

@@ -1,38 +0,0 @@
-{
-  "title": {
-    "message": "Task",
-    "description": "The title in the navbar"
-  },
-  "item.label.Installation": {
-    "message": "Instalación",
-    "description": "Navbar item with label Installation"
-  },
-  "item.label.Usage": {
-    "message": "Guía de uso",
-    "description": "Navbar item with label Usage"
-  },
-  "item.label.API": {
-    "message": "API",
-    "description": "Navbar item with label API"
-  },
-  "item.label.Donate": {
-    "message": "Donar",
-    "description": "Navbar item with label Donate"
-  },
-  "item.label.GitHub": {
-    "message": "GitHub",
-    "description": "Navbar item with label GitHub"
-  },
-  "item.label.Twitter": {
-    "message": "Twitter",
-    "description": "Navbar item with label Twitter"
-  },
-  "item.label.Mastodon": {
-    "message": "Mastodon",
-    "description": "Navbar item with label Mastodon"
-  },
-  "item.label.Discord": {
-    "message": "Discord",
-    "description": "Navbar item with label Discord"
-  }
-}

docs/i18n/fr-FR/code.json

@@ -1,396 +0,0 @@
-{
-  "theme.ErrorPageContent.title": {
-    "message": "Cette page a rencontré un problème.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Veuillez réessayer",
-    "description": "The label of the button to try again when the page crashed"
-  },
-  "theme.NotFound.title": {
-    "message": "Page non trouvée",
-    "description": "The title of the 404 page"
-  },
-  "theme.NotFound.p1": {
-    "message": "Nous n'avons pas trouvé ce que vous recherchiez.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Veuillez contacter le propriétaire du site qui vous a lié à l'URL d'origine et lui faire savoir que son lien est rompu.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.admonition.note": {
-    "message": "note",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "conseils",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.danger": {
-    "message": "danger",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "info",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.caution": {
-    "message": "attention",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Retour en haut de la page",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archiver",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archiver",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Navigation dans la page de la liste des blogs",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Nouvelles entrées",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Anciennes Entrées",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Navigation dans la page d'article du blog",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Article récent",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Article plus ancien",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.blog.post.plurals": {
-    "message": "Un article|{count} articles",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} tagués avec « {tagName} »",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "Voir tous les tags",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Basculer entre le mode sombre et le mode clair (actuellement {mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "mode sombre",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "mode clair",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Page d’accueil",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Fil d'Ariane",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription": {
-    "message": "{count} éléments",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Navigation dans les pages",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Précédent",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Suivant",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "Un document tagué|{count} documents tagués",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} avec \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Version : {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "Ceci est une documentation non publiée pour la version {versionLabel} de {siteTitle}.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "Ceci est la documentation de {siteTitle} {versionLabel}, qui n'est plus activement maintenue.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "Pour une documentation à jour, consultez la {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "dernière version",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Éditer cette page",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Lien direct vers l'entête",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " le {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " par {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Dernière mise à jour{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versions",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Tags:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Fermer",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Navigation dans les articles récents du blog",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copié",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copier le code dans le presse-papiers",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copier",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Basculer le retour à la ligne automatique",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.toggleCollapsedCategoryAriaLabel": {
-    "message": "Plier/Déplier la catégorie '{label}' de la barre latérale",
-    "description": "The ARIA label to toggle the collapsible sidebar category"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Langues",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "Sur cette page",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.blog.post.readMore": {
-    "message": "En Savoir Plus",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "En savoir plus sur {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "Une minute de lecture|{readingTime} minutes de lecture",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Réduire la barre latérale",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Réduire la barre latérale",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Fermer la barre de navigation",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "Retour au menu principal",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Afficher/Masquer la barre de navigation",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Déplier le menu latéral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Déplier le menu latéral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.SearchBar.seeAll": {
-    "message": "Voir les {count} résultats"
-  },
-  "theme.SearchPage.documentsFound.plurals": {
-    "message": "Un document trouvé |{count} documents trouvés",
-    "description": "Pluralized label for \"{count} documents found\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.SearchPage.existingResultsTitle": {
-    "message": "Résultats de la recherche pour \"{query}\"",
-    "description": "The search page title for non-empty query"
-  },
-  "theme.SearchPage.emptyResultsTitle": {
-    "message": "Rechercher dans la documentation",
-    "description": "The search page title for empty query"
-  },
-  "theme.SearchPage.inputPlaceholder": {
-    "message": "Saisissez votre recherche ici",
-    "description": "The placeholder for search page input"
-  },
-  "theme.SearchPage.inputLabel": {
-    "message": "Rechercher",
-    "description": "The ARIA label for search page input"
-  },
-  "theme.SearchPage.algoliaLabel": {
-    "message": "Recherche par Algolia",
-    "description": "The ARIA label for Algolia mention"
-  },
-  "theme.SearchPage.noResultsText": {
-    "message": "Aucun résultat trouvé",
-    "description": "The paragraph for empty search result"
-  },
-  "theme.SearchPage.fetchingNewResults": {
-    "message": "Recherche de nouveaux résultats...",
-    "description": "The paragraph for fetching new search results"
-  },
-  "theme.SearchBar.label": {
-    "message": "Rechercher",
-    "description": "The ARIA label and placeholder for search button"
-  },
-  "theme.SearchModal.searchBox.resetButtonTitle": {
-    "message": "Effacer la recherche",
-    "description": "The label and ARIA label for search box reset button"
-  },
-  "theme.SearchModal.searchBox.cancelButtonText": {
-    "message": "Annuler",
-    "description": "The label and ARIA label for search box cancel button"
-  },
-  "theme.SearchModal.startScreen.recentSearchesTitle": {
-    "message": "Récent",
-    "description": "The title for recent searches"
-  },
-  "theme.SearchModal.startScreen.noRecentSearchesText": {
-    "message": "Pas de recherches récentes",
-    "description": "The text when no recent searches"
-  },
-  "theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
-    "message": "Enregistrer cette recherche",
-    "description": "The label for save recent search button"
-  },
-  "theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
-    "message": "Supprimer cette recherche de l'historique",
-    "description": "The label for remove recent search button"
-  },
-  "theme.SearchModal.startScreen.favoriteSearchesTitle": {
-    "message": "Favoris",
-    "description": "The title for favorite searches"
-  },
-  "theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
-    "message": "Supprimer cette recherche des favoris",
-    "description": "The label for remove favorite search button"
-  },
-  "theme.SearchModal.errorScreen.titleText": {
-    "message": "Impossible de récupérer les résultats",
-    "description": "The title for error screen of search modal"
-  },
-  "theme.SearchModal.errorScreen.helpText": {
-    "message": "Vous devriez vérifier votre connexion réseau.",
-    "description": "The help text for error screen of search modal"
-  },
-  "theme.SearchModal.footer.selectText": {
-    "message": "sélectionner",
-    "description": "The explanatory text of the action for the enter key"
-  },
-  "theme.SearchModal.footer.selectKeyAriaLabel": {
-    "message": "Touche Entrée",
-    "description": "The ARIA label for the Enter key button that makes the selection"
-  },
-  "theme.SearchModal.footer.navigateText": {
-    "message": "naviguer",
-    "description": "The explanatory text of the action for the Arrow up and Arrow down key"
-  },
-  "theme.SearchModal.footer.navigateUpKeyAriaLabel": {
-    "message": "Flèche du haut",
-    "description": "The ARIA label for the Arrow up key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.navigateDownKeyAriaLabel": {
-    "message": "Flèche du bas",
-    "description": "The ARIA label for the Arrow down key button that makes the navigation"
-  },
-  "theme.SearchModal.footer.closeText": {
-    "message": "fermer",
-    "description": "The explanatory text of the action for Escape key"
-  },
-  "theme.SearchModal.footer.closeKeyAriaLabel": {
-    "message": "Touche Echap",
-    "description": "The ARIA label for the Escape key button that close the modal"
-  },
-  "theme.SearchModal.footer.searchByText": {
-    "message": "Rechercher par",
-    "description": "The text explain that the search is making by Algolia"
-  },
-  "theme.SearchModal.noResultsScreen.noResultsText": {
-    "message": "Aucun résultat pour",
-    "description": "The text explains that there are no results for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.suggestedQueryText": {
-    "message": "Essayez de rechercher",
-    "description": "The text for the suggested query when no results are found for the following search"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsText": {
-    "message": "Pensez-vous que cette requête aurait dû retourner des résultats ?",
-    "description": "The text for the question where the user thinks there are missing results"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
-    "message": "Faites-le nous savoir.",
-    "description": "The text for the link to report missing results"
-  },
-  "theme.SearchModal.placeholder": {
-    "message": "Rechercher dans la documentation",
-    "description": "The placeholder of the input of the DocSearch pop-up modal"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Accéder directement au contenu principal",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Tags",
-    "description": "The title of the tag list page"
-  }
-}

docs/i18n/fr-FR/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md

@@ -1,93 +0,0 @@
----
-title: Introducing Experiments
-description: A look at where task is, where it's going and how we're going to get there.
-slug: task-in-2023
-authors:
-  - pd93
-tags:
-  - experiments
-  - breaking-changes
-  - roadmap
-  - v4
-image: https://i.imgur.com/mErPwqL.png
-hide_table_of_contents: false
----
-
-Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
-
-<!--truncate-->
-
-## :calendar: So, what have we been up to?
-
-Over the past 12 months or so, [@andreynering][] (Author and maintainer of the project) and I ([@pd93][]) have been working in our spare time to maintain and improve v3 of Task and we've made some amazing progress. Here are just some of the things we've released in that time:
-
-- An official [extension for VS Code][vscode-task].
-- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
-- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
-- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
-- A series of refactors to the core codebase to make it more maintainable and extensible.
-- Loads of bug fixes and improvements.
-- An integration with [Crowdin][crowdin]. Work is in progress on making our docs available in **7 new languages** (Special thanks to all our translators for the huge help with this!).
-- And much, much more! :sparkles:
-
-We're also working on adding some really exciting and highly requested features to Task such as having the ability to run remote Taskfiles ([#1317](https://github.com/go-task/task/issues/1317)).
-
-None of this would have been possible without the [150 or so (and growing) contributors][contributors] to the project, numerous sponsors and a passionate community of users. Together we have more than doubled the number of GitHub stars to over 8400 :star: since the beginning of 2022 and this continues to accelerate. We can't thank you all enough for your help and support! :rocket:
-
-[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
-
-## What's next? :thinking:
-
-It's extremely motivating to see so many people using and loving Task. However, in this time we've also seen an increase in the number of issues and feature requests. In particular, issues that require some kind of breaking change to Task. This isn't a bad thing, but as we grow we need to be more responsible about how we address these changes in a way that ensures stability and compatibility for existing users and their Taskfiles.
-
-At this point you're probably thinking something like:
-
-> "But you use [semantic versioning][semver] - Just release a new major version with your breaking changes."
-
-And you'd be right... sort of. In theory, this sounds great, but the reality is that we don't have the time to commit to a major overhaul of Task in one big bang release. This would require a colossal amount of time and coordination and with full time jobs and personal lives to tend to, this is a difficult commitment to make. Smaller, more frequent major releases are also a significant inconvenience for users as they have to constantly keep up-to-date with our breaking changes. Fortunately, there is a better way.
-
-## What's going to change? :monocle:
-
-Going forwards, breaking changes will be allowed into _minor_ versions of Task as "experimental features". To access these features users will need opt-in by enabling feature flags. This will allow us to release new features slowly and gather feedback from the community before making them the default behavior in a future major release.
-
-To prepare users for the next major release, we will maintain a list of [deprecated features][deprecations] and [experiments][experiments] on our docs website and publish information on how to migrate to the new behavior.
-
-You can read the [full breaking change proposal][breaking-change-proposal] and view all the [current experiments and their status][experiments-project] on GitHub including the [Gentle Force][gentle-force-experiment] and [Remote Taskfiles][remote-taskfiles-experiment] experiments.
-
-## What will happen to v2/v3 features?
-
-v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase and focus on new functionality instead.
-
-When v4 is released, we will continue to support v3 for a period of time (bug fixes etc). However, since we are moving from a backward-compatibility model to a forwards-compatibility model, **v4 itself will not be backwards compatible with v3**.
-
-## v4 When? :eyes:
-
-:man_shrugging: When it's ready.
-
-In all seriousness, we don't have a timeline for this yet. We'll be working on the most serious deficiencies of the v3 API first and regularly evaluating the state of the project. When we feel its in a good, stable place and we have a clear upgrade path for users and a number of stable experiments, we'll start to think about v4.
-
-## :wave: Final thoughts
-
-Task is growing fast and we're excited to see where it goes next. We hope that the steps we're taking to improve the project and our process will help us to continue to grow. As always, if you have any questions or feedback, we encourage you to comment on or open [issues][issues] and [discussions][discussions] on GitHub. Alternatively, you can join us on [Discord][discord].
-
-I plan to write more of these blog posts in the future on a variety of Task-related topics, so make sure to check in occasionally and see what we're up to!
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[vscode-task]: https://github.com/go-task/vscode-task
-[crowdin]: https://crowdin.com
-[contributors]: https://github.com/go-task/task/graphs/contributors
-[semver]: https://semver.org
-[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
-[@andreynering]: https://github.com/andreynering
-[@pd93]: https://github.com/pd93
-[experiments]: https://taskfile.dev/experiments
-[deprecations]: https://taskfile.dev/deprecations
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
-[issues]: https://github.com/go-task/task/issues
-[discussions]: https://github.com/go-task/task/discussions
-[discord]: https://discord.gg/6TY36E39UK
-[experiments-project]: https://github.com/orgs/go-task/projects/1
-[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
-[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317

docs/i18n/fr-FR/docusaurus-plugin-content-blog/authors.yml

@@ -1,10 +0,0 @@
-andreynering:
-  name: Andrey Nering
-  title: Mainteneur de Task
-  url: https://github.com/andreynering
-  image_url: https://github.com/andreynering.png
-pd93:
-  name: Pete Davison
-  title: Mainteneur de Task
-  url: https://github.com/pd93
-  image_url: https://github.com/pd93.png

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current.json

@@ -1,6 +0,0 @@
-{
-  "version.label": {
-    "message": "Suivant",
-    "description": "The label for version current"
-  }
-}

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/changelog.md

@@ -1,573 +0,0 @@
----
-slug: /changelog/
-sidebar_position: 14
----
-
-# Changelog
-
-## v3.33.1 - 2023-12-21
-
-- Added support for looping over map variables with the [Any Variables experiment](https://taskfile.dev/experiments/any_variables) enabled (#1435, #1437 by @pd93).
-- Fixed a bug where dynamic variables were causing errors during fast compilation (#1435, #1437 by @pd93)
-
-## v3.33.0 - 2023-12-20
-
-- Added [Any Variables experiment](https://taskfile.dev/experiments/any-variables) (#1415, #1421 by @pd93).
-- Updated Docusaurus to v3 (#1432 by @pd93).
-- Added `aliases` to `--json` flag output (#1430, #1431 by @pd93).
-- Added new `CLI_FORCE` special variable containing whether the `--force` or `--force-all` flags were set (#1412, #1434 by @pd93).
-
-## v3.32.0 - 2023-11-29
-
-- Added ability to exclude some files from `sources:` by using `exclude:` (#225,
-
-  # 1324 by @pd93 and @andreynering).
-- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default (#1317, #1345 by @pd93).
-- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1345 by @pd93).
-- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` (#1273, #1377 by @andreynering).
-- Fix `schema.json` to make `silent` valid in `cmds` that use `for` (#1385,
-
-  # 1386 by @iainvm).
-- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` (#1348, #1368 by @amancevice).
-
-## v3.31.0 - 2023-10-07
-
-- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1344 by @pd93).
-- Add ability to set `watch: true` in a task to automatically run it in watch mode (#231, #1361 by @andreynering).
-- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored (#1356 by @butuzov).
-- Fixed a nil pointer error when running a Taskfile with no contents (#1341,
-
-  # 1342 by @pd93).
-- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version (#1342 by @pd93).
-- Increased limit of maximum task calls from 100 to 1000 for now, as some people have been reaching this limit organically now that we have loops. This check exists to detect recursive calls, but will be removed in favor of a better algorithm soon (#1321, #1332).
-- Fixed templating on descriptions on `task --list` (#1343 by @blackjid).
-- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted (#1337, #1338 by @sylv-io).
-
-## v3.30.1 - 2023-09-14
-
-- Fixed a regression where some special variables weren't being set correctly (#1331, #1334 by @pd93).
-
-## v3.30.0 - 2023-09-13
-
-- Prep work for Remote Taskfiles (#1316 by @pd93).
-- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft (#1152, #1317 by @pd93).
-- Improve performance of content checksuming on `sources:` by replacing md5 with [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking change because checksums will be invalidated when upgrading to this release (#1325 by @ReillyBrogan).
-
-## v3.29.1 - 2023-08-26
-
-- Update to Go 1.21 (bump minimum version to 1.20) (#1302 by @pd93)
-- Fix a missing a line break on log when using `--watch` mode (#1285, #1297 by @FilipSolich).
-- Fix `defer` on JSON Schema (#1288 by @calvinmclean and @andreynering).
-- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` (#1046, #1205, #1250, #1293, #1312, #1274 by @andarto, #1309 by @andreynering).
-- Fix bug on `--status` flag. Running this flag should not have side-effects: it should not update the checksum on `.task`, only report its status (#1305,
-
-  # 1307 by @visciang, #1313 by @andreynering).
-
-## v3.28.0 - 2023-07-24
-
-- Added the ability to [loop over commands and tasks](https://taskfile.dev/usage/#looping-over-values) using `for` (#82, #1220 by @pd93).
-- Fixed variable propagation in multi-level includes (#778, #996, #1256 by @hudclark).
-- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly (#1266, #1270 by @pd93).
-- Fixed a `nil` panic when a dependency was commented out or left empty (#1263 by @neomantra).
-
-## v3.27.1 - 2023-06-30
-
-- Fix panic when a `.env` directory (not file) is present on current directory (#1244, #1245 by @pd93).
-
-## v3.27.0 - 2023-06-29
-
-- Allow Taskfiles starting with lowercase characters (#947, #1221 by @pd93).
-  - e.g. `taskfile.yml`, `taskfile.yaml`, `taskfile.dist.yml` & `taskfile.dist.yaml`
-- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). (#1190, by @sounisi5011).
-- Added the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) as a draft (#1200, #1216 by @pd93).
-- Added an `--experiments` flag to allow you to see which experiments are enabled (#1242 by @pd93).
-- Added ability to specify which variables are required in a task (#1203, #1204 by @benc-uk).
-
-## v3.26.0 - 2023-06-10
-
-- Only rewrite checksum files in `.task` if the checksum has changed (#1185,
-
-  # 1194 by @deviantintegral).
-- Added [experiments documentation](https://taskfile.dev/experiments) to the website (#1198 by @pd93).
-- Deprecated `version: 2` schema. This will be removed in the next major release (#1197, #1198, #1199 by @pd93).
-- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task (#100, #1163 by @MaxCheetham, [Documentation](https://taskfile.dev/usage/#warning-prompts)).
-- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task (#1130, #1131 by @timdp).
-
-## v3.25.0 - 2023-05-22
-
-- Support `silent:` when calling another tasks (#680, #1142 by @danquah).
-- Improve PowerShell completion script (#1168 by @trim21).
-- Add more languages to the website menu and show translation progress percentage (#1173 by @misitebao).
-- Starting on this release, official binaries for FreeBSD will be available to download (#1068 by @andreynering).
-- Fix some errors being unintendedly supressed (#1134 by @clintmod).
-- Fix a nil pointer error when `version` is omitted from a Taskfile (#1148,
-
-  # 1149 by @pd93).
-- Fix duplicate error message when a task does not exists (#1141, #1144 by @pd93).
-
-## v3.24.0 - 2023-04-15
-
-- Fix Fish shell completion for tasks with aliases (#1113 by @patricksjackson).
-- The default branch was renamed from `master` to `main` (#1049, #1048 by @pd93).
-- Fix bug where "up-to-date" logs were not being omitted for silent tasks (#546,
-
-  # 1107 by @danquah).
-- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` (#1098 by @misery).
-- More improvements to the release tool (#1096 by @pd93).
-- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter (#1099 by @pd93)
-- Add `--sort` flag for use with `--list` and `--list-all` (#946, #1105 by @pd93).
-- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error (#1114 by @pd93).
-
-## v3.23.0 - 2023-03-26
-
-Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by @pd93! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
-
-> **NOTE:** The extension _requires_ v3.23.0 to be installed in order to work.
-
-- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available (#1057, #1058 by @misitebao).
-- Added task location data to the `--json` flag output (#1056 by @pd93)
-- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` (#1062 by @misitebao).
-- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments (#1040, #1059 by @dhanusaputra).
-- Fix the value of `{{.CHECKSUM}}` variable in status (#1076, #1080 by @pd93).
-- Fixed deep copy implementation (#1072 by @pd93)
-- Created a tool to assist with releases (#1086 by @pd93).
-
-## v3.22.0 - 2023-03-10
-
-- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), #1029 by @andreynering).
-- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code (#664, #1022 by @jaedle).
-- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` (#840, #1035 by @harelwa, #1037 by @pd93).
-- Refactored and decoupled fingerprinting from the main Task executor (#1039 by @pd93).
-- Fixed deadlock issue when using `run: once` (#715, #1025 by @theunrepentantgeek).
-
-## v3.21.0 - 2023-02-22
-
-- Added new `TASK_VERSION` special variable (#990, #1014 by @ja1code).
-- Fixed a bug where tasks were sometimes incorrectly marked as internal (#1007 by @pd93).
-- Update to Go 1.20 (bump minimum version to 1.19) (#1010 by @pd93)
-- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY (#1003 by @automation-stack)
-
-## v3.20.0 - 2023-01-14
-
-- Improve behavior and performance of status checking when using the `timestamp` mode (#976, #977 by @aminya).
-- Performance optimizations were made for large Taskfiles (#982 by @pd93).
-- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins (#908, #929 by @pd93, [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
-- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped (#978, #980 by @leaanthony).
-
-## v3.19.1 - 2022-12-31
-
-- Small bug fix: closing `Taskfile.yml` once we're done reading it (#963, #964 by @HeCorr).
-- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file (#961, #971 by @pd93).
-- Fixed a bug where watch intervals set in the Taskfile were not being respected (#969, #970 by @pd93)
-- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future (#936 by @davidalpert, #764).
-
-## v3.19.0 - 2022-12-05
-
-- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm#2](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm#3](https://github.com/go-task/go-npm/pull/3)).
-- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos (#289, #920).
-- Add task-level `dotenv` support (#389, #904).
-- It's now possible to use global level variables on `includes` (#942, #943).
-- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [@DeronW](https://github.com/DeronW). Thanks!
-
-## v3.18.0 - 2022-11-12
-
-- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts (#919).
-- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output (#806, #890).
-- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` (#661, #815).
-
-## v3.17.0 - 2022-10-14
-
-- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found (#867, #880).
-- Now YAML parse errors will print which Taskfile failed to parse (#885, #887).
-- Add ability to set `aliases` for tasks and namespaces (#268, #340, #879).
-- Improvements to Fish shell completion (#897).
-- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag (#813, #865).
-- Add colored output to `--list`, `--list-all` and `--summary` flags (#845,
-
-  # 874).
-- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` (#603, #877).
-
-## v3.16.0 - 2022-09-29
-
-- Add `npm` as new installation method: `npm i -g @go-task/cli` (#870, #871, [npm package](https://www.npmjs.com/package/@go-task/cli)).
-- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` (#818).
-
-## v3.15.2 - 2022-09-08
-
-- Fix error when using variable in `env:` introduced in the previous release (#858, #866).
-- Fix handling of `CLI_ARGS` (`--`) in Bash completion (#863).
-- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion (#861).
-
-## v3.15.0 - 2022-09-03
-
-- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature (#215, #857, [Documentation](https://taskfile.dev/api/#special-variables)).
-- Follow symlinks on `sources` (#826, #831).
-- Improvements and fixes to Bash completion (#835, #844).
-
-## v3.14.1 - 2022-08-03
-
-- Always resolve relative include paths relative to the including Taskfile (#822, #823).
-- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) (#803).
-
-## v3.14.0 - 2022-07-08
-
-- Add ability to override the `.task` directory location with the `TASK_TEMP_DIR` environment variable.
-- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` (#568, #792).
-- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order (#779).
-- Starting on this release, ARM architecture binaries are been released to Snap as well (#795).
-- i386 binaries won't be available anymore on Snap because Ubuntu removed the support for this architecture.
-- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays (#785, [mvdan/sh#884](https://github.com/mvdan/sh/issues/884), [mvdan/sh#893](https://github.com/mvdan/sh/pull/893)).
-
-## v3.13.0 - 2022-06-13
-
-- Added `-n` as an alias to `--dry` (#776, #777).
-- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work (#458, #479, #728, #769).
-- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran (#755).
-
-## v3.12.1 - 2022-05-10
-
-- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` (#717).
-
-## v3.12.0 - 2022-03-31
-
-- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description (#691).
-- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level (#390, #623, #656).
-- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information (#677).
-
-## v3.11.0 - 2022-02-19
-
-- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information (#647, #651).
-- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information (#498, #666).
-
-## v3.10.0 - 2022-01-04
-
-- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description (#383, #401).
-- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer),
-
-  # 475, #626).
-- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix (#642, #644, #645).
-- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! (#183, #184, #369, #584,
-
-  # 621).
-- Fixed error when computing a variable when the task directory do not exist yet (#481, #579).
-
-## v3.9.2 - 2021-12-02
-
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows (#619, [mvdan/sh#768](https://github.com/mvdan/sh/issues/768), [mvdan/sh#769](https://github.com/mvdan/sh/pull/769)).
-
-## v3.9.1 - 2021-11-28
-
-- Add logging in verbose mode for when a task starts and finishes (#533, #588).
-- Fix an issue with preconditions and context errors (#597, #598).
-- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many (#613).
-- Fix nil pointer when `cmd:` was left empty (#612, #614).
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains two relevant fixes:
-  - Fix quote of empty strings in `shellQuote` (#609, [mvdan/sh#763](https://github.com/mvdan/sh/issues/763)).
-  - Fix issue of wrong environment variable being picked when there's another very similar one (#586, [mvdan/sh#745](https://github.com/mvdan/sh/pull/745)).
-- Install shell completions automatically when installing via Homebrew (#264, #592, [go-task/homebrew-tap#2](https://github.com/go-task/homebrew-tap/pull/2)).
-
-## v3.9.0 - 2021-10-02
-
-- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh#727](https://github.com/mvdan/sh/pull/727), [mvdan/sh#737](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3@v3.4.0/syntax#Quote))
-- In this version [mvdan.cc/sh](https://github.com/mvdan/sh) was upgraded with some small fixes and features
-  - The `read -p` flag is now supported (#314, [mvdan/sh#551](https://github.com/mvdan/sh/issues/551), [mvdan/sh#772](https://github.com/mvdan/sh/pull/722))
-  - The `pwd -P` and `pwd -L` flags are now supported (#553, [mvdan/sh#724](https://github.com/mvdan/sh/issues/724), [mvdan/sh#728](https://github.com/mvdan/sh/pull/728))
-  - The `$GID` environment variable is now correctly being set (#561, [mvdan/sh#723](https://github.com/mvdan/sh/pull/723))
-
-## v3.8.0 - 2021-09-26
-
-- Add `interactive: true` setting to improve support for interactive CLI apps (#217, #563).
-- Fix some `nil` errors (#534, #573).
-- Add ability to declare an included Taskfile as optional (#519, #552).
-- Add support for including Taskfiles in the home directory by using `~` (#539, #557).
-
-## v3.7.3 - 2021-09-04
-
-- Add official support to Apple M1 (#564, #567).
-- Our [official Homebrew tap](https://github.com/go-task/homebrew-tap) will support more platforms, including Apple M1
-
-## v3.7.0 - 2021-07-31
-
-- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! (#53, #359).
-
-## v3.6.0 - 2021-07-10
-
-- Allow using both `sources:` and `status:` in the same task (#411, #427, #477).
-- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` (#517).
-
-## v3.5.0 - 2021-07-04
-
-- Add support for interpolation in `dotenv:` (#433, #434, #453).
-
-## v3.4.3 - 2021-05-30
-
-- Add support for the `NO_COLOR` environment variable. (#459, [fatih/color#137](https://github.com/fatih/color/pull/137)).
-- Fix bug where sources were not considering the right directory in `--watch` mode (#484, #485).
-
-## v3.4.2 - 2021-04-23
-
-- On watch, report which file failed to read (#472).
-- Do not try to catch SIGKILL signal, which are not actually possible (#476).
-- Improve version reporting when building Task from source using Go Modules (#462, #473).
-
-## v3.4.1 - 2021-04-17
-
-- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example (#467).
-- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code (#135).
-- Print task name before the command in the log output (#398).
-
-## v3.3.0 - 2021-03-20
-
-- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable (#327).
-- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. (#345).
-
-## v3.2.2 - 2021-01-12
-
-- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags (#332).
-- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment (#425).
-- Fixed environment from .env files not being available as variables (#379).
-- The install script is now working for ARM platforms (#428).
-
-## v3.2.1 - 2021-01-09
-
-- Fixed some bugs and regressions regarding dynamic variables and directories (#426).
-- The [slim-sprig](https://github.com/go-task/slim-sprig) package was updated with the upstream [sprig](https://github.com/Masterminds/sprig).
-
-## v3.2.0 - 2021-01-07
-
-- Fix the `.task` directory being created in the task directory instead of the Taskfile directory (#247).
-- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile (#384).
-- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now (#423, #365).
-
-## v3.1.0 - 2021-01-03
-
-- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute (#412).
-- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux (#375, #418).
-- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them (#393).
-- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line (#403).
-
-## v3.0.1 - 2020-12-26
-
-- Allow use as a library by moving the required packages out of the `internal` directory (#358).
-- Do not error if a specified dotenv file does not exist (#378, #385).
-- Fix panic when you have empty tasks in your Taskfile (#338, #362).
-
-## v3.0.0 - 2020-08-16
-
-- On `v3`, all CLI variables will be considered global variables (#336, #341)
-- Add support to `.env` like files (#324, #356).
-- Add `label:` to task so you can override the task name in the logs (#321,
-
-  # 337).
-- Refactor how variables work on version 3 (#311).
-- Disallow `expansions` on v3 since it has no effect.
-- `Taskvars.yml` is not automatically included anymore.
-- `Taskfile_{{OS}}.yml` is not automatically included anymore.
-- Allow interpolation on `includes`, so you can manually include a Taskfile based on operation system, for example.
-- Expose `.TASK` variable in templates with the task name (#252).
-- Implement short task syntax (#194, #240).
-- Added option to make included Taskfile run commands on its own directory (#260, #144)
-- Taskfiles in version 1 are not supported anymore (#237).
-- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile (#246).
-- Changed default method from `timestamp` to `checksum` (#246).
-- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` (#216).
-- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% (#219).
-- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc (#207).
-
-## v2.8.1 - 2020-05-20
-
-- Fix error code for the `--help` flag (#300, #330).
-- Print version to stdout instead of stderr (#299, #329).
-- Supress `context` errors when using the `--watch` flag (#313, #317).
-- Support templating on description (#276, #283).
-
-## v2.8.0 - 2019-12-07
-
-- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel (#266).
-- Fixed bug where calling the `task` CLI only informing global vars would not execute the `default` task.
-- Add hability to silent all tasks by adding `silent: true` a the root of the Taskfile.
-
-## v2.7.1 - 2019-11-10
-
-- Fix error being raised when `exit 0` was called (#251).
-
-## v2.7.0 - 2019-09-22
-
-- Fixed panic bug when assigning a global variable (#229, #243).
-- A task with `method: checksum` will now re-run if generated files are deleted (#228, #238).
-
-## v2.6.0 - 2019-07-21
-
-- Fixed some bugs regarding minor version checks on `version:`.
-- Add `preconditions:` to task (#205).
-- Create directory informed on `dir:` if it doesn't exist (#209, #211).
-- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) (#221).
-- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap#1](https://github.com/go-task/homebrew-tap/pull/1)).
-
-## v2.5.2 - 2019-05-11
-
-- Reverted YAML upgrade due issues with CRLF on Windows (#201, [go-yaml/yaml#450](https://github.com/go-yaml/yaml/issues/450)).
-- Allow setting global variables through the CLI (#192).
-
-## 2.5.1 - 2019-04-27
-
-- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues (#114, #190, #200).
-- Upgraded [go-yaml/yaml](https://github.com/go-yaml/yaml) from v2 to v3.
-
-## v2.5.0 - 2019-03-16
-
-- We moved from the taskfile.org domain to the new fancy taskfile.dev domain. While stuff is being redirected, we strongly recommend to everyone that use [this install script](https://taskfile.dev/#/installation?id=install-script) to use the new taskfile.dev domain on scripts from now on.
-- Fixed to the ZSH completion (#182).
-- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) (#180).
-
-## v2.4.0 - 2019-02-21
-
-- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` (#161, #172).
-- Add flag to override the `output` option (#173).
-- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled (#166).
-- Fix file timestamp issue when the file name has spaces (#176).
-- Mitigating path expanding issues on Windows (#170).
-
-## v2.3.0 - 2019-01-02
-
-- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) (#152).
-- Fixed issue with file/directory globing (#153).
-- Added ability to globally set environment variables (#138, #159).
-
-## v2.2.1 - 2018-12-09
-
-- This repository now uses Go Modules (#143). We'll still keep the `vendor` directory in sync for some time, though;
-- Fixing a bug when the Taskfile has no tasks but includes another Taskfile (#150);
-- Fix a bug when calling another task or a dependency in an included Taskfile (#151).
-
-## v2.2.0 - 2018-10-25
-
-- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) (#98)
-  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on #98.
-- Task now have a dedicated documentation site: https://taskfile.org
-  - Thanks to [Docsify](https://docsify.js.org/) for making this pretty easy. To check the source code, just take a look at the [docs](https://github.com/go-task/task/tree/main/docs) directory of this repository. Contributions to the documentation is really appreciated.
-
-## v2.1.1 - 2018-09-17
-
-- Fix suggestion to use `task --init` not being shown anymore (when a `Taskfile.yml` is not found)
-- Fix error when using checksum method and no file exists for a source glob (#131)
-- Fix signal handling when the `--watch` flag is given (#132)
-
-## v2.1.0 - 2018-08-19
-
-- Add a `ignore_error` option to task and command (#123)
-- Add a dry run mode (`--dry` flag) (#126)
-
-## v2.0.3 - 2018-06-24
-
-- Expand environment variables on "dir", "sources" and "generates" (#116)
-- Fix YAML merging syntax (#112)
-- Add ZSH completion (#111)
-- Implement new `output` option. Please check out the [documentation](https://github.com/go-task/task#output-syntax)
-
-## v2.0.2 - 2018-05-01
-
-- Fix merging of YAML anchors (#112)
-
-## v2.0.1 - 2018-03-11
-
-- Fixes panic on `task --list`
-
-## v2.0.0 - 2018-03-08
-
-Version 2.0.0 is here, with a new Taskfile format.
-
-Please, make sure to read the [Taskfile versions](https://github.com/go-task/task/blob/main/TASKFILE_VERSIONS.md) document, since it describes in depth what changed for this version.
-
-- New Taskfile version 2 (#77)
-- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` (#66)
-- Small improvements and fixes
-
-## v1.4.4 - 2017-11-19
-
-- Handle SIGINT and SIGTERM (#75);
-- List: print message with there's no task with description;
-- Expand home dir ("~" symbol) on paths (#74);
-- Add Snap as an installation method;
-- Move examples to its own repo;
-- Watch: also walk on tasks called on on "cmds", and not only on "deps";
-- Print logs to stderr instead of stdout (#68);
-- Remove deprecated `set` keyword;
-- Add checksum based status check, alternative to timestamp based.
-
-## v1.4.3 - 2017-09-07
-
-- Allow assigning variables to tasks at run time via CLI (#33)
-- Added suport for multiline variables from sh (#64)
-- Fixes env: remove square braces and evaluate shell (#62)
-- Watch: change watch library and few fixes and improvements
-- When use watching, cancel and restart long running process on file change (#59 and #60)
-
-## v1.4.2 - 2017-07-30
-
-- Flag to set directory of execution
-- Always echo command if is verbose mode
-- Add silent mode to disable echoing of commands
-- Fixes and improvements of variables (#56)
-
-## v1.4.1 - 2017-07-15
-
-- Allow use of YAML for dynamic variables instead of $ prefix
-  - `VAR: {sh: echo Hello}` instead of `VAR: $echo Hello`
-- Add `--list` (or `-l`) flag to print existing tasks
-- OS specific Taskvars file (e.g. `Taskvars_windows.yml`, `Taskvars_linux.yml`, etc)
-- Consider task up-to-date on equal timestamps (#49)
-- Allow absolute path in generates section (#48)
-- Bugfix: allow templating when calling deps (#42)
-- Fix panic for invalid task in cyclic dep detection
-- Better error output for dynamic variables in Taskvars.yml (#41)
-- Allow template evaluation in parameters
-
-## v1.4.0 - 2017-07-06
-
-- Cache dynamic variables
-- Add verbose mode (`-v` flag)
-- Support to task parameters (overriding vars) (#31) (#32)
-- Print command, also when "set:" is specified (#35)
-- Improve task command help text (#35)
-
-## v1.3.1 - 2017-06-14
-
-- Fix glob not working on commands (#28)
-- Add ExeExt template function
-- Add `--init` flag to create a new Taskfile
-- Add status option to prevent task from running (#27)
-- Allow interpolation on `generates` and `sources` attributes (#26)
-
-## v1.3.0 - 2017-04-24
-
-- Migrate from os/exec.Cmd to a native Go sh/bash interpreter
-  - This is a potentially breaking change if you use Windows.
-  - Now, `cmd` is not used anymore on Windows. Always use Bash-like syntax for your commands, even on Windows.
-- Add "ToSlash" and "FromSlash" to template functions
-- Use functions defined on github.com/Masterminds/sprig
-- Do not redirect stdin while running variables commands
-- Using `context` and `errgroup` packages (this will make other tasks to be cancelled, if one returned an error)
-
-## v1.2.0 - 2017-04-02
-
-- More tests and Travis integration
-- Watch a task (experimental)
-- Possibility to call another task
-- Fix "=" not being reconized in variables/environment variables
-- Tasks can now have a description, and help will print them (#10)
-- Task dependencies now run concurrently
-- Support for a default task (#16)
-
-## v1.1.0 - 2017-03-08
-
-- Support for YAML, TOML and JSON (#1)
-- Support running command in another directory (#4)
-- `--force` or `-f` flag to force execution of task even when it's up-to-date
-- Detection of cyclic dependencies (#5)
-- Support for variables (#6, #9, #14)
-- Operation System specific commands and variables (#13)
-
-## v1.0.0 - 2017-02-28
-
-- Add LICENSE file

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/community.md

@@ -1,33 +0,0 @@
----
-slug: /community/
-sidebar_position: 9
----
-
-# Communauté
-
-Certains travaux d'amélioration de l'écosystème Task sont réalisés par la communauté, que ce soit des méthodes d'installation ou des intégrations avec l'éditeur de code. Moi (l'auteur) suis reconnaissant envers tout le monde qui m'aide à améliorer l'expérience globale.
-
-## Traductions
-
-Nous utilisons [Crowdin](https://crowdin.com/project/taskfile) pour traduire nos documents.
-
-## Intégrations
-
-Un grand nombre de nos intégrations sont apportées et maintenues par la communauté. Vous pouvez voir la liste complète des intégrations de la communauté [ici](/integrations#community-integrations).
-
-## Méthodes d'installation
-
-Certaines méthodes d'installation sont maintenues par un tiers :
-
-- [GitHub Actions](https://github.com/arduino/setup-task) by @arduino
-- [AUR](https://aur.archlinux.org/packages/go-task-bin) by @carlsmedstad
-- [Scoop](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json)
-- [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
-- [NixOS](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/go-task/default.nix)
-- [Conda](https://github.com/conda-forge/go-task-feedstock/)
-
-## Plus d’infos
-
-Aussi, merci à tous les [contributeurs](https://github.com/go-task/task/graphs/contributors), [contributeurs financiers](https://opencollective.com/task), tous ceux qui [ont signalé des bugs](https://github.com/go-task/task/issues?q=is%3Aissue) et [ont répondu aux questions](https://github.com/go-task/task/discussions).
-
-Si vous voyez quelque chose qui manque dans ce document, veuillez soumettre une pull request.

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/contributing.md

@@ -1,101 +0,0 @@
----
-slug: /contributing/
-sidebar_position: 11
----
-
-# Contributing
-
-Contributions to Task are very welcome, but we ask that you read this document before submitting a PR.
-
-:::note
-
-This document applies to the core [Task][task] repository _and_ [Task for Visual Studio Code][vscode-task].
-
-:::
-
-## Before you start
-
-- **Check existing work** - Is there an existing PR? Are there issues discussing the feature/change you want to make? Please make sure you consider/address these discussions in your work.
-- **Backwards compatibility** - Will your change break existing Taskfiles? It is much more likely that your change will merged if it backwards compatible. Is there an approach you can take that maintains this compatibility? If not, consider opening an issue first so that API changes can be discussed before you invest your time into a PR.
-- **Experiments** - If there is no way to make your change backward compatible then there is a procedure to introduce breaking changes into minor versions. We call these "\[experiments\]\[experiments\]". If you're intending to work on an experiment, then please read the \[experiments workflow\]\[experiments-workflow\] document carefully and submit a proposal first.
-
-## 1. Setup
-
-- **Go** - Task is written in [Go][go]. We always support the latest two major Go versions, so make sure your version is recent enough.
-- **Node.js** - [Node.js][nodejs] is used to host Task's documentation server and is required if you want to run this server locally. It is also required if you want to contribute to the Visual Studio Code extension.
-- **Yarn** - [Yarn][yarn] is the Node.js package manager used by Task.
-
-## 2. Making changes
-
-- **Code style** - Try to maintain the existing code style where possible. Go code should be formatted by [`gofumpt`][gofumpt] and linted using [`golangci-lint`][golangci-lint]. Any Markdown or TypeScript files should be formatted and linted by [Prettier][prettier]. This style is enforced by our CI to ensure that we have a consistent style across the project. You can use the `task lint` command to lint the code locally and the `task lint:fix` command to automatically fix any issues that are found.
-- **Documentation** - Ensure that you add/update any relevant documentation. See the [updating documentation](#updating-documentation) section below.
-- **Tests** - Ensure that you add/update any relevant tests and that all tests are passing before submitting the PR. See the [writing tests](#writing-tests) section below.
-
-### Running your changes
-
-To run Task with working changes, you can use `go run ./cmd/task`. To run a development build of task against a test Taskfile in `testdata`, you can use `go run ./cmd/task --dir ./testdata/<my_test_dir> <task_name>`.
-
-To run Task for Visual Studio Code, you can open the project in VSCode and hit F5 (or whatever you debug keybind is set to). This will open a new VSCode window with the extension running. Debugging this way is recommended as it will allow you to set breakpoints and step through the code. Otherwise, you can run `task package` which will generate a `.vsix` file that can be used to manually install the extension.
-
-### Updating documentation
-
-Task uses [Docusaurus][docusaurus] to host a documentation server. The code for this is located in the core Task repository. This can be setup and run locally by using `task docs` (requires `nodejs` & `yarn`). All content is written in Markdown and is located in the `docs/docs` directory. All Markdown documents should have an 80 character line wrap limit (enforced by Prettier).
-
-When making a change, consider whether a change to the [Usage Guide](/usage) is necessary. This document contains descriptions and examples of how to use Task features. If you're adding a new feature, try to find an appropriate place to 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 the [Taskfile Styleguide](/styleguide).
-
-If you added a new field, command or flag, ensure that you add it to the [API Reference](/api). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
-
-### Writing tests
-
-A lot of Task's tests are held in the `task_test.go` file in the project root and this is where you'll most likely want to add new ones too. Most of these tests also have a subdirectory in the `testdata` directory where any Taskfiles/data required to run the tests are stored.
-
-When making a changes, consider whether new tests are required. These tests should ensure that the functionality you are adding will continue to work in the future. Existing tests may also need updating if you have changed Task's behavior.
-
-You may also consider adding unit tests for any new functions you have added. The unit tests should follow the Go convention of being location in a file named `*_test.go` in the same package as the code being tested.
-
-## 3. Committing your code
-
-Try to write meaningful commit messages and avoid having too many commits on the PR. Most PRs should likely have a single commit (although for bigger PRs it may be reasonable to split it in a few). Git squash and rebase is your friend!
-
-If you're not sure how to format your commit message, check out [Conventional Commits][conventional-commits]. This style is not enforced, but it is a good way to make your commit messages more readable and consistent.
-
-## 4. Submitting a PR
-
-- **Describe your changes** - Ensure that you provide a comprehensive description of your changes.
-- **Issue/PR links** - Link any previous work such as related issues or PRs. Please describe how your changes differ to/extend this work.
-- **Examples** - Add any examples or screenshots that you think are useful to demonstrate the effect of your changes.
-- **Draft PRs** - If your changes are incomplete, but you would like to discuss them, open the PR as a draft and add a comment to start a discussion. Using comments rather than the PR description allows the description to be updated later while preserving any discussions.
-
-## FAQ
-
-> I want to contribute, where do I start?
-
-Take a look at the list of [open issues for Task][task-open-issues] or [Task for Visual Studio Code][vscode-task-open-issues]. We have a [good first issue][good-first-issue] label for simpler issues that are ideal for first time contributions.
-
-All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](/community).
-
-> I'm stuck, where can I get help?
-
-If you have questions, feel free to ask them in the `#help` forum channel on our [Discord server][discord-server] or open a [Discussion][discussion] on GitHub.
-
----
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[task]: https://github.com/go-task/task
-[vscode-task]: https://github.com/go-task/vscode-task
-[go]: https://go.dev
-[gofumpt]: https://github.com/mvdan/gofumpt
-[golangci-lint]: https://golangci-lint.run
-[prettier]: https://prettier.io
-[nodejs]: https://nodejs.org/en/
-[yarn]: https://yarnpkg.com/
-[docusaurus]: https://docusaurus.io
-[json-schema]: https://github.com/go-task/task/blob/main/docs/static/schema.json
-[task-open-issues]: https://github.com/go-task/task/issues
-[vscode-task-open-issues]: https://github.com/go-task/vscode-task/issues
-[good-first-issue]: https://github.com/go-task/task/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
-[discord-server]: https://discord.gg/6TY36E39UK
-[discussion]: https://github.com/go-task/task/discussions
-[conventional-commits]: https://www.conventionalcommits.org

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/deprecations.md

@@ -1,12 +0,0 @@
----
-slug: /deprecations/
-sidebar_position: 7
----
-
-# Dépréciations
-
-Au fur et à mesure que Task évolue, certaines de ses fonctionnalités peuvent se montrer obsolètes. Cela peut être dû au fait qu'elles ne sont plus utiles, parce qu'une autre fonctionnalité l'a remplacée ou à cause d'un changement dans la façon dont la tâche fonctionne.
-
-Lorsque cela se produit, nous marquons la fonctionnalité comme obsolète. Cela signifie que sera supprimé dans une future version de Task. La fonctionnalité continuera de fonctionner en attendant, mais il vous est fortement recommandé de ne plus l'utiliser et de planifier un plan de migration pour changer toutes les tâches pouvant l'utiliser.
-
-Vous pouvez afficher une liste complète des dépréciations actives dans la section "Dépréciations" de la barre latérale.

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/template.md

@@ -1,22 +0,0 @@
----
-#This is a template for an experiments documentation
-#Copy this page and fill in the details as necessary
-title: '--- Template ---'
-sidebar_position: -1 #Always push to the top
-draft: true #Hide in production
----
-
-# \{Name of Deprecated Feature\} (#\{Issue\})
-
-:::warning
-
-This deprecation breaks the following functionality:
-
-- \{list any existing functionality that will be broken by this deprecation\}
-- \{if there are no breaking changes, remove this admonition\}
-
-:::
-
-\{Short description of the feature/behavior and why it is being deprecated\}
-
-\{Short explanation of any replacement features/behaviors and how users should migrate to it\}

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md

@@ -1,25 +0,0 @@
----
-slug: /deprecations/version-2-schema/
----
-
-# Version 2 Schema (#1197)
-
-:::warning
-
-This deprecation breaks the following functionality:
-
-- Any Taskfiles that use the version 2 schema
-- `Taskvar.yml` files
-
-:::
-
-The Taskfile version 2 schema was introduced in March 2018 and replaced by version 3 in August 2019. In May 2023 [we published a deprecation notice][deprecation-notice] for the version 2 schema on the basis that the vast majority of users had already upgraded to version 3 and removing support for version 2 would allow us to tidy up the codebase and focus on new functionality instead.
-
-In December 2023, the final version of Task that supports the version 2 schema ([v3.33.0][v3.33.0]) was published and all legacy code was removed from Task's main branch. To use a more recent version of Task, you will need to ensure that your Taskfile uses the version 3 schema instead. A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][v3.0.0].
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[v3.0.0]: https://github.com/go-task/task/releases/tag/v3.0.0
-[v3.33.0]: https://github.com/go-task/task/releases/tag/v3.33.0
-[deprecation-notice]: https://github.com/go-task/task/issues/1197

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/donate.md

@@ -1,44 +0,0 @@
----
-slug: /donate/
-sidebar_position: 16
----
-
-# Faire un don
-
-Si vous trouvez ce projet utile, vous pouvez envisager de faire un don en utilisant l'un des canaux listés ci-dessous.
-
-C'est juste une façon de nous dire "merci", il ne vous donnera pas d'avantages comme une priorité élevée sur des problèmes ou des choses similaires.
-
-Les entreprises qui font un don d'au moins 50$/mois seront présentées comme un "Sponsor Or" sur la page d'accueil du site and sur le README du dépôt GitHub. Prenez contact avec [@andreynering][] avec le logo que vous voulez afficher. Cependant, les entreprises suspectes (jeux, casinos, etc) ne seront pas autorisées.
-
-## Sponsors GitHub
-
-La façon préférée de faire un don aux mainteneurs du projet est d'utiliser les sponsors GitHub. Vous pouvez utiliser le lien suivant pour faire votre don. We suggest a 50/50 split to each maintainer of the total amount you plan to donate to the project.
-
-- [@andreynering](https://github.com/sponsors/andreynering)
-- [@pd93](https://github.com/sponsors/pd93)
-
-## Open Collective
-
-Si vous préférez [Open Collective](https://opencollective.com/task) vous pouvez faire un don en utilisant ces liens :
-
-- [2$ par mois](https://opencollective.com/task/contribute/backer-4034/checkout)
-- [5$ par mois](https://opencollective.com/task/contribute/supporter-8404/checkout)
-- [20$ par mois](https://opencollective.com/task/contribute/sponsor-4035/checkout)
-- [50$ par mois](https://opencollective.com/task/contribute/sponsor-28775/checkout)
-- [Valeur personnalisée - option de don unique prise en charge](https://opencollective.com/task/donate)
-
-## PayPal
-
-Vous pouvez aussi faire un don à [@andreynering][] via PayPal :
-
-- [N'importe quelle valeur - Don unique](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=GSVDU63RKG45A&currency_code=USD&source=url)
-
-## PIX (Brésil uniquement)
-
-Et si vous êtes Brésilien, vous pouvez également faire un don à [@andreynering][] via PIX en [utilisant ce QR Code](/img/pix.png).
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[@andreynering]: https://github.com/andreynering

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/any_variables.md

@@ -1,206 +0,0 @@
----
-slug: /experiments/any-variables/
----
-
-# Any Variables (#1415)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any
-time_. We strongly recommend that you do not use these features in a production
-environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- Dynamically defined variables (using the `sh` keyword)
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable:
-`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
-][enabling-experiments] for more information.
-
-:::
-
-Currently, Task only supports string variables. This experiment allows you to
-specify and use the following variable types:
-
-- `string`
-- `bool`
-- `int`
-- `float`
-- `array`
-- `map`
-
-This allows you to have a lot more flexibility in how you use variables in
-Task's templating engine. For example:
-
-Evaluating booleans:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      BOOL: false
-    cmds:
-      - '{{if .BOOL}}echo foo{{end}}'
-```
-
-Arithmetic:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      INT: 10
-      FLOAT: 3.14159
-    cmds:
-      - 'echo {{add .INT .FLOAT}}'
-```
-
-Ranging:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      ARRAY: [1, 2, 3]
-    cmds:
-      - 'echo {{range .ARRAY}}{{.}}{{end}}'
-```
-
-There are many more templating functions which can be used with the new types of
-variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
-
-## Looping over variables
-
-Previously, you would have to use a delimiter separated string to loop over an
-arbitrary list of items in a variable and split them by using the `split` subkey
-to specify the delimiter:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: 'foo,bar,baz'
-    cmds:
-      - for:
-          var: LIST
-          split: ','
-        cmd: echo {{.ITEM}}
-```
-
-Because this experiment adds support for "collection-type" variables, the `for`
-keyword has been updated to support looping over arrays directly:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: [foo, bar, baz]
-    cmds:
-      - for:
-          var: LIST
-        cmd: echo {{.ITEM}}
-```
-
-This also works for maps. When looping over a map we also make an additional
-`{{.KEY}}` variable availabe that holds the string value of the map key.
-Remember that maps are unordered, so the order in which the items are looped
-over is random:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      MAP:
-        KEY_1:
-          SUBKEY: sub_value_1
-        KEY_2:
-          SUBKEY: sub_value_2
-        KEY_3:
-          SUBKEY: sub_value_3
-    cmds:
-      - for:
-          var: MAP
-        cmd: echo {{.KEY}} {{.ITEM.SUBKEY}}
-```
-
-String splitting is still supported and remember that for simple cases, you have
-always been able to loop over an array without using variables at all:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    cmds:
-      - for: [foo, bar, baz]
-        cmd: echo {{.ITEM}}
-```
-
-## Migration
-
-Taskfiles with dynamically defined variables via the `sh` subkey will no longer
-work with this experiment enabled. In order to keep using dynamically defined
-variables, you will need to migrate your Taskfile to use the new syntax.
-
-Previously, you might have defined a dynamic variable like this:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR:
-        sh: 'echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-With this experiment enabled, you will need to remove the `sh` subkey and define
-your command as a string that begins with a `$`. This will instruct Task to
-interpret the string as a command instead of a literal value and the variable
-will be populated with the output of the command. For example:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR: '$echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-If your current Taskfile contains a string variable that begins with a `$`, you
-will now need to escape the `$` with a backslash (`\`) to stop Task from
-executing it as a command.
-
-<!-- prettier-ignore-start -->
-
-[enabling-experiments]: /experiments/#enabling-experiments
-
-[slim-sprig]: https://go-task.github.io/slim-sprig/
-
-<!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/any_variables.mdx

@@ -1,162 +0,0 @@
----
-slug: /experiments/any-variables/
----
-
-# Any Variables
-
--   Issue: #1415
--   Environment variable: `TASK_X_ANY_VARIABLES=1`
--   Breaks:
-    -   Dynamically defined variables (using the `sh` keyword)
-
-Currently, Task only supports string variables. This experiment allows you to
-specify and use the following variable types:
-
--   `string`
--   `bool`
--   `int`
--   `float`
--   `array`
--   `map`
-
-This allows you to have a lot more flexibility in how you use variables in
-Task's templating engine. For example:
-
-Evaluating booleans:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      BOOL: false
-    cmds:
-      - '{{if .BOOL}}echo foo{{end}}'
-```
-
-Arithmetic:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      INT: 10
-      FLOAT: 3.14159
-    cmds:
-      - 'echo {{add .INT .FLOAT}}'
-```
-
-Ranging:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      ARRAY: [1, 2, 3]
-    cmds:
-      - 'echo {{range .ARRAY}}{{.}}{{end}}'
-```
-
-There are many more templating functions which can be used with the new types of
-variables. For a full list, see the
-[slim-sprig][slim-sprig] documentation.
-
-## Looping over variables
-
-Previously, you would have to use a delimiter separated string to loop over an
-arbitrary list of items in a variable and split them by using the `split` subkey
-to specify the delimiter:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: 'foo,bar,baz'
-    cmds:
-      - for:
-          var: LIST
-          split: ','
-        cmd: echo {{.ITEM}}
-```
-
-Because this experiment adds support for array variables, the `for` keyword has
-been updated to support looping over arrays directly:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    vars:
-      LIST: [foo, bar, baz]
-    cmds:
-      - for:
-          var: LIST
-        cmd: echo {{.ITEM}}
-```
-
-String splitting is still supported and remember that for simple cases, you have
-always been able to loop over an array without using variables at all:
-
-```yaml
-version: 3
-
-tasks:
-  foo:
-    cmds:
-      - for: [foo, bar, baz]
-        cmd: echo {{.ITEM}}
-```
-
-## Migration
-
-Taskfiles with dynamically defined variables via the `sh` subkey will no longer
-work with this experiment enabled. In order to keep using dynamically defined
-variables, you will need to migrate your Taskfile to use the new syntax.
-
-Previously, you might have defined a dynamic variable like this:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR:
-        sh: 'echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-With this experiment enabled, you will need to remove the `sh` subkey and define
-your command as a string that begins with a `$`. This will instruct Task to
-interpret the string as a command instead of a literal value and the variable
-will be populated with the output of the command. For example:
-
-```yaml
-version: 3
-
-task:
-  foo:
-    vars:
-      CALCULATED_VAR: '$echo hello'
-    cmds:
-      - 'echo {{.CALCULATED_VAR}}'
-```
-
-If your current Taskfile contains a string variable that begins with a `$`, you
-will now need to escape the `$` with a backslash (`\`) to stop Task from
-executing it as a command.
-
-<!-- prettier-ignore-start -->
-
-[slim-sprig]: https://go-task.github.io/slim-sprig/
-
-<!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/experiments.md

@@ -1,79 +0,0 @@
----
-slug: /experiments/
-sidebar_position: 6
----
-
-# Expérimentations
-
-:::caution
-
-Toutes les fonctionnalités expérimentales sont sujettes à des changements brisant la fonctionnalité et/ou à la suppression de cette dernière _à tout moment _. Nous vous recommandons fortement de ne pas utiliser ces fonctionnalités dans en production. Ils sont seulement destinés à être testés et obtenir des retours dessus.
-
-:::
-
-Afin de permettre à Task d'évoluer rapidement, nous déployons des changements cassants sur des versions mineures activables par des options expérimentales. Cela nous permet d'obtenir des retours sur des changements brisants des fonctionnalités avant de les livrer dans une version majeure. Ce document décrit l'ensemble actuel de fonctionnalités expérimentales et leur statut dans le [workflow](#workflow).
-
-Vous pouvez consulter une liste complète des expérimentations en cours dans la section "Expérimentations" de la barre latérale .
-
-## Enabling Experiments
-
-You can enable an experimental feature by doing one of the following:
-
-1. Utiliser la variable d'environnement pertinente devant une commande Task. Par exemple, `TASK_X_{FEATURE}=1 task {my-task}`. Ceci est prévu pour faire appel à une expérimentation durant une seule commande Task afin de tester une fonctionnalité expérimentale.
-1. Utiliser la variable d'environnement pertinente dans vos "dotfiles" (par exemple `.bashrc`, `.zshrc` etc.). Ceci est destiné à l'activation permanente des fonctionnalités expérimentales dans votre environnement.
-1. Création d'un fichier `.env` dans le même répertoire que votre fichier Taskfile contenant les variables d'environnement pertinentes pour vos tests. This allows you to enable an experimental feature at a project level. For example:
-
-```shell title=".env"
-TASK_X_FEATURE=1
-```
-
-## Current Experimental Features and Deprecations
-
-Each section below details an experiment or deprecation and explains what the flags/environment variables to enable the experiment are and how the feature's behavior will change. It will also explain what you need to do to migrate any existing Taskfiles to the new behavior.
-
-## Workflow
-
-Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
-
-The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
-
-### 1. Proposal
-
-All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
-
-### 2. Draft
-
-Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
-
-:::note
-
-During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
-
-:::
-
-### 3. Candidate
-
-Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
-
-### 4. Stable
-
-Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
-
-### 5. Released
-
-When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
-
-### Abandoned / Superseded
-
-If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
-[draft]: https://img.shields.io/badge/experiment:%20draft-purple
-[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
-[stable]: https://img.shields.io/badge/experiment:%20stable-purple
-[released]: https://img.shields.io/badge/experiment:%20released-purple
-[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
-[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/gentle_force.md

@@ -1,36 +0,0 @@
----
-slug: /experiments/gentle-force/
----
-
-# Gentle Force (#1200)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- The `--force` flag
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_FORCE=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
-
-This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
-
-If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md

@@ -1,66 +0,0 @@
----
-slug: /experiments/remote-taskfiles/
----
-
-# Remote Taskfiles (#1317)
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-This experiment allows you to specify a remote Taskfile URL when including a Taskfile. For example:
-
-```yaml
-version: '3'
-
-includes:
-  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
-```
-
-This works exactly the same way that including a local file does. Any tasks in the remote Taskfile will be available to run from your main Taskfile via the namespace `my-remote-namespace`. For example, if the remote file contains the following:
-
-```yaml
-version: '3'
-
-tasks:
-  hello:
-    silent: true
-    cmds:
-      - echo "Hello from the remote Taskfile!"
-```
-
-and you run `task my-remote-namespace:hello`, it will print the text: "Hello from the remote Taskfile!" to your console.
-
-## Security
-
-Running commands from sources that you do not control is always a potential security risk. For this reason, we have added some checks when using remote Taskfiles:
-
-1. When running a task from a remote Taskfile for the first time, Task will print a warning to the console asking you to check that you are sure that you trust the source of the Taskfile. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the remote Taskfile will run and further calls to the remote Taskfile will not prompt you again.
-2. Whenever you run a remote Taskfile, Task will create and store a checksum of the file that you are running. If the checksum changes, then Task will print another warning to the console to inform you that the contents of the remote file has changed. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the checksum will be updated and the remote Taskfile will run.
-
-Sometimes you need to run Task in an environment that does not have an interactive terminal, so you are not able to accept a prompt. In these cases you are able to tell task to accept these prompts automatically by using the `--yes` flag. Before enabling this flag, you should:
-
-1. Be sure that you trust the source and contents of the remote Taskfile.
-2. Consider using a pinned version of the remote Taskfile (e.g. A link containing a commit hash) to prevent Task from automatically accepting a prompt that says a remote Taskfile has changed.
-
-Task currently supports both `http` and `https` URLs. However, the `http` requests will not execute by default unless you run the task with the `--insecure` flag. This is to protect you from accidentally running a remote Taskfile that is hosted on and unencrypted connection. Sources that are not protected by TLS are vulnerable to [man-in-the-middle attacks][man-in-the-middle-attacks] and should be avoided unless you know what you are doing.
-
-## Caching & Running Offline
-
-Whenever you run a remote Taskfile, the latest copy will be downloaded from the internet and cached locally. If for whatever reason, you lose access to the internet, you will still be able to run your tasks by specifying the `--offline` flag. This will tell Task to use the latest cached version of the file instead of trying to download it. You are able to use the `--download` flag to update the cached version of the remote files without running any tasks.
-
-By default, Task will timeout requests to download remote files after 10 seconds and look for a cached copy instead. This timeout can be configured by setting the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will set the timeout to 5 seconds.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments
-[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/template.md

@@ -1,39 +0,0 @@
----
-#This is a template for an experiments documentation
-#Copy this page and fill in the details as necessary
-title: '--- Template ---'
-sidebar_position: -1 #Always push to the top
-draft: true #Hide in production
----
-
-# \{Name of Experiment\} (#\{Issue\})
-
-:::caution
-
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
-
-:::
-
-:::warning
-
-This experiment breaks the following functionality:
-
-- \{list any existing functionality that will be broken by this experiment\}
-- \{if there are no breaking changes, remove this admonition\}
-
-:::
-
-:::info
-
-To enable this experiment, set the environment variable: `TASK_X_{feature}=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
-
-:::
-
-\{Short description of the feature\}
-
-\{Short explanation of how users should migrate to the new behavior\}
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/workflow.md

@@ -1,50 +0,0 @@
----
-slug: /experiments/workflow/
----
-
-# Workflow
-
-Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
-
-The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
-
-## 1. Proposal
-
-All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
-
-## 2. Draft
-
-Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
-
-:::note
-
-During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
-
-:::
-
-## 3. Candidate
-
-Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
-
-## 4. Stable
-
-Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
-
-## 5. Released
-
-When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
-
-## Abandoned / Superseded
-
-If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
-[draft]: https://img.shields.io/badge/experiment:%20draft-purple
-[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
-[stable]: https://img.shields.io/badge/experiment:%20stable-purple
-[released]: https://img.shields.io/badge/experiment:%20released-purple
-[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
-[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/faq.md

@@ -1,89 +0,0 @@
----
-slug: /faq/
-sidebar_position: 15
----
-
-# FAQ
-
-Cette page contient une liste de question fréquemment posée à propos de Task.
-
-## Why won't my task update my shell environment?
-
-This is a limitation of how shells work. Task runs as a subprocess of your current shell, so it can't change the environment of the shell that started it. This limitation is shared by other task runners and build tools too.
-
-A common way to work around this is to create a task that will generate output that can be parsed by your shell. For example, to set an environment variable on your shell you can write a task like this:
-
-```yaml
-my-shell-env:
-  cmds:
-    - echo "export FOO=foo"
-    - echo "export BAR=bar"
-```
-
-Now run `eval $(task my-shell-env)` and the variables `$FOO` and `$BAR` will be available in your shell.
-
-## I can't reuse my shell in a task's commands
-
-Task runs each command as a separate shell process, so something you do in one command won't effect any future commands. For example, this won't work:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - a=foo
-      - echo $a
-      # outputs ""
-```
-
-To work around this you can either use a multiline command:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - |
-        a=foo
-        echo $a
-      # outputs "foo"
-```
-
-Or for more complex multi-line commands it is recommended to move your code into a separate file and call that instead:
-
-```yaml
-version: '3'
-
-tasks:
-  foo:
-    cmds:
-      - ./foo-printer.bash
-```
-
-```bash
-#!/bin/bash
-a=foo
-echo $a
-```
-
-## 'x' builtin command doesn't work on Windows
-
-The default shell on Windows (`cmd` and `powershell`) do not have commands like `rm` and `cp` available as builtins. This means that these commands won't work. If you want to make your Taskfile fully cross-platform, you'll need to work around this limitation using one of the following methods:
-
-- Use the `{{OS}}` function to run an OS-specific script.
-- Use something like `{{if eq OS "windows"}}powershell {{end}}<my_cmd>` to detect windows and run the command in Powershell directly.
-- Use a shell on Windows that supports these commands as builtins, such as [Git Bash][git-bash] or [WSL][wsl].
-
-We want to make improvements to this part of Task and the issues below track this work. Constructive comments and contributions are very welcome!
-
-- #197
-- [mvdan/sh#93](https://github.com/mvdan/sh/issues/93)
-- [mvdan/sh#97](https://github.com/mvdan/sh/issues/97)
-
-<!-- prettier-ignore-start -->
-
-<!-- prettier-ignore-end -->
-[git-bash]: https://gitforwindows.org/
-[wsl]: https://learn.microsoft.com/en-us/windows/wsl/install