What about the ability to "hide" a task?

[photex]

As I've started to really use pixi quite a lot, I've been making use the ability to compose a tasks from some core tasks with args.

For example, I have some tools that convert audio files or pack textures. I have a root tasks to clone, build, and then a task to run the tool. Then I have the primary tasks to run the tool on specific source assets, and a final "meta" task to run all of those if desired.

When I run pixi run to see a list of defined tasks, it's an explosion of various tasks that hinder the discoverability of what should actually be used to build and run anything.

It could be helpful then to have an attribute on tasks that shouldn't be shown by default in this case.

Knowing that pixi run can list the available tasks is also a sort of feature that provides an easier view to read than pixi task list and since we have both pixi task list and pixi run I'm not fully sure the correct way to surface the ability to mark some tasks as "hidden" or "internal" and additionally make it possible to see all tasks when a user might want to run a task marked as such.

So just to be clear and reiterate, the idea is only to have a way to affect the default display of tasks that someone might be expected to run in a project.

[ruben-arts]

Adding _ to a task name would hide it from those commands.

[photex]

I’d love to 👍

[lucascolley]

gentle ping @photex :) I was just thinking about this again today!

[photex]

:D I was waddling a bit trying to decide where to place it. Seems like a small section in advanced_tasks.md in the "Task Arguments" section before the section on MiniJinja.

But opening the PR and having the discussion there is probably the most productive thing to do.

[lucascolley]

I think I would place it below the depends-on section of that page, as the main use-case for hidden tasks is as dependencies of other tasks.

[photex]

#4230