task
task copied to clipboard
go-task
A task runner / simpler Make alternative written in Go
This PR greatly improves the error reporting of YAML issues by surfacing the real parsing errors from `yaml.v3` and providing a syntax highlighted snippet of the error and its location....
Bumps [golang.org/x/term](https://github.com/golang/term) from 0.19.0 to 0.20.0. Commits 46c790f go.mod: update golang.org/x dependencies See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Node 16 is deprecated so I've bump checkout / setup-go and setup-arduino to the lastest version
I've introduce a new concept in node, the `filename`. This will allow us to store remote checksums/cached files with a more user-friendly filename Linked to : - https://github.com/go-task/task/issues/1317
Fixes #1616 I've gone with `TASK_EXE` instead of `TASK_EXECUTABLE` as suggested simply because its a bit shorter. Thoughts welcome.
This works fine: ```yaml FRAMEWORK_DEP_FILES: '{{.FRAMEWORK_DEP_FILE_LIST | join ","}}' ``` but this raises an error: ```yaml FRAMEWORK_DEP_FILES: ref: .FRAMEWORK_DEP_FILE_LIST | join "," ``` ``` template: resolver:1: function "join" not defined...
[sprig](https://github.com/Masterminds/sprig/issues/396) is the library that we use for template functions. We forked it on [slim-sprig](https://github.com/go-task/slim-sprig) because the original imports too many packages and also had many functions that do not...
Initially reported at https://github.com/go-task/task/issues/112, YAML merging don't work when using the strict mode. I rolled back to normal mode to fix the issue. Since strict mode is important to disallow...
I've added a command to clear the cache for remote files. I've made the choice to disallow using download and clear-cache at the same time because clear-cache should be used...
> [!WARNING] > 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....