We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain your question here go-task is pretty cool compared to mage and make.
i was thinking about how the the husky hooks can be integrated with go-tasks.
here is a project that uses a task files extensively: https://github.com/yomorun/yomo
https://github.com/yomorun/yomo/blob/master/Taskfile.yml is the root shows some standard ci related things.
https://github.com/yomorun/yomo/blob/master/example/1-pipeline/Taskfile.yml shows how many processes and pipelines can be kicked off. you don't need to open multiple terminals. It manages the supervisions .
SO perhaps there is merit in using go task and husky together, so that you can manage the git hooks from the go task file.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Explain your question here
go-task is pretty cool compared to mage and make.
i was thinking about how the the husky hooks can be integrated with go-tasks.
here is a project that uses a task files extensively: https://github.com/yomorun/yomo
https://github.com/yomorun/yomo/blob/master/Taskfile.yml is the root shows some standard ci related things.
https://github.com/yomorun/yomo/blob/master/example/1-pipeline/Taskfile.yml shows how many processes and pipelines can be kicked off. you don't need to open multiple terminals. It manages the supervisions .
SO perhaps there is merit in using go task and husky together, so that you can manage the git hooks from the go task file.
The text was updated successfully, but these errors were encountered: