feat: support lowercase Taskfiles (#1221)

This commit is contained in:
Pete Davison
2023-06-17 18:38:53 +01:00
committed by GitHub
parent d82b0faca1
commit 5e78171d3e
4 changed files with 15 additions and 4 deletions

View File

@@ -2,6 +2,9 @@
## Unreleased ## Unreleased
- Allow Taskfiles starting with lowercase characters (#947, #1221 by @pd93).
- e.g. `taskfile.yml`, `taskfile.yaml`, `taskfile.dist.yml` &
`taskfile.dist.yaml`
- Bug fixed were made to the - Bug fixed were made to the
[npm installation method](https://taskfile.dev/installation/#npm). [npm installation method](https://taskfile.dev/installation/#npm).
(#1190, by @sounisi5011). (#1190, by @sounisi5011).
@@ -19,8 +22,8 @@
[Documentation](https://taskfile.dev/usage/#warning-prompts)). [Documentation](https://taskfile.dev/usage/#warning-prompts)).
- Added support for single command task syntax. With this change, it's now - 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 possible to declare just `cmd:` in a task, avoiding the more complex
`cmds: []` when you have only a single command for that task `cmds: []` when you have only a single command for that task (#1130, #1131 by
(#1130, #1131 by @timdp). @timdp).
## v3.25.0 - 2023-05-22 ## v3.25.0 - 2023-05-22

View File

@@ -128,7 +128,7 @@ func run() error {
pflag.BoolVarP(&flags.color, "color", "c", true, "Colored output. Enabled by default. Set flag to false or use NO_COLOR=1 to disable.") pflag.BoolVarP(&flags.color, "color", "c", true, "Colored output. Enabled by default. Set flag to false or use NO_COLOR=1 to disable.")
pflag.IntVarP(&flags.concurrency, "concurrency", "C", 0, "Limit number tasks to run concurrently.") pflag.IntVarP(&flags.concurrency, "concurrency", "C", 0, "Limit number tasks to run concurrently.")
pflag.DurationVarP(&flags.interval, "interval", "I", 0, "Interval to watch for changes.") pflag.DurationVarP(&flags.interval, "interval", "I", 0, "Interval to watch for changes.")
pflag.BoolVarP(&flags.global, "global", "g", false, "Runs global Taskfile, from $HOME/Taskfile.{yml,yaml}.") pflag.BoolVarP(&flags.global, "global", "g", false, "Runs global Taskfile, from $HOME/{T,t}askfile.{yml,yaml}.")
pflag.Parse() pflag.Parse()
if flags.version { if flags.version {

View File

@@ -43,9 +43,13 @@ If you omit a task name, "default" will be assumed.
Task will look for the following file names, in order of priority: Task will look for the following file names, in order of priority:
- Taskfile.yml - Taskfile.yml
- taskfile.yml
- Taskfile.yaml - Taskfile.yaml
- taskfile.yaml
- Taskfile.dist.yml - Taskfile.dist.yml
- taskfile.dist.yml
- Taskfile.dist.yaml - Taskfile.dist.yaml
- taskfile.dist.yaml
The intention of having the `.dist` variants is to allow projects to have one The intention of having the `.dist` variants is to allow projects to have one
committed version (`.dist`) while still allowing individual users to override committed version (`.dist`) while still allowing individual users to override
@@ -85,7 +89,7 @@ will be brought up.
If you call Task with the `--global` (alias `-g`) flag, it will look for your If you call Task with the `--global` (alias `-g`) flag, it will look for your
home directory instead of your working directory. In short, Task will look for a home directory instead of your working directory. In short, Task will look for a
Taskfile on either `$HOME/Taskfile.yml` or `$HOME/Taskfile.yaml` paths. Taskfile that matches `$HOME/{T,t}askfile.{yml,yaml}` .
This is useful to have automation that you can run from anywhere in your system! This is useful to have automation that you can run from anywhere in your system!

View File

@@ -21,9 +21,13 @@ var (
defaultTaskfiles = []string{ defaultTaskfiles = []string{
"Taskfile.yml", "Taskfile.yml",
"taskfile.yml",
"Taskfile.yaml", "Taskfile.yaml",
"taskfile.yaml",
"Taskfile.dist.yml", "Taskfile.dist.yml",
"taskfile.dist.yml",
"Taskfile.dist.yaml", "Taskfile.dist.yaml",
"taskfile.dist.yaml",
} }
) )