The actions performed by a task are often too complex or specific, and the task name cannot describe the task’s action sufficiently well. Moreover,
build scripts usually consist of many tasks - whether explicitly defined or implicitly by the applied plugins - so a structure is required to help the
user navigate through existing tasks.
Therefore, tasks should define a description and group to provide documentation and categorization for the user.
What is the potential impact?
Improve task discoverability
Users can find tasks easier and understand their purpose if they contain a description and are grouped into categories.
