Question 1

How do I run goyek tasks in parallel?

Accepted Answer

Set the Task.Parallel field for safe concurrent tasks and use middleware.BufferParallel to keep output readable. However, parallelism requires careful design to avoid race conditions, as noted in best practices.

Question 2

goyek vs Mage: which should I use for my Go project?

Accepted Answer

goyek is better if you prefer a library-based approach without code generation, while Mage uses build tags and magic discovery. goyek offers more explicit control and easier debugging, as explained in the rationale.

Question 3

How to pass command-line arguments to a goyek task?

Accepted Answer

Use Go's flag package to define flags, as shown in the example with -msg. Flags are parsed globally, and tasks can access them via the defined variables in the action function.

Question 4

Can goyek handle deployment workflows, not just builds?

Accepted Answer

Yes, goyek is a general task runner; its dependency system and middleware make it suitable for operational scripts, deployment pipelines, and other automation beyond builds, as mentioned in the philosophy.

Question 5

How to handle errors and clean up resources in goyek tasks?

Accepted Answer

Use a.Error to mark tasks as failed without stopping, a.Fatal for immediate termination, and a.Cleanup for resource release. Context is managed via a.Context for cancellation, per best practices.

Question 6

What's the best way to structure task dependencies in goyek?

Accepted Answer

Define small, focused tasks and use the Deps field to compose them. This mirrors good software design practices, making pipelines modular and testable, as recommended in best practices.

goyek

What is goyek?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions