Take a special recipe as group

[xingheng]

I want to add a few commands related on a group like this:

[group('app')]
edit:
    echo "edit in app"

[group('app')]
run:
    echo "run app"

This is good, but it cannot define another edit recipe for another group, so are there any solutions to mark the group name as a top-level recipe name then I can run it like: just app edit & just app run?
Maybe we could add an option like [group('app', invoke_as_recipe=True)] to do that?

[casey]

If you want to invoke a group of recipes, you can define a new recipe with those recipes as dependencies:

lint:

test:

ci: test lint

Group names do not conflict with recipe names, which means that we couldn't allow invoking groups on the command line, since you could have a group named foo and a recipe named foo.

Although perhaps we could introduce a setting which made recipe/group name conflicts an error, and thus allow invoking groups on the command line.

I'm not sure if I'd want the above though. Currently, groups are about documentation, not semantics, so, for example, you might have a recipe which is definitely involved in testing, but is very slow, so you couldn't add it to the test group without breaking the common workflow of running just test to invoke all the recipes in the test group.

[xingheng]

@casey my "group" means it can manage a few recipes with a scope, just like a namespace, and I want to use the same recipe under the different groups, this makes the command in bash just app1 run more meaningful I think.
Any alternative solutions or suggestions?