Support task names completion on command line

code + test + doc

... when a project just starts...

CACHEDIR builtin config item shall be added (relatively to ROOTDIR one)

... instead of <> (reserved for repo references)

Something like

refs:
    - https://github.com/dynod/nmk-base/archive/refs/heads/main.zip!nmk-base-main/plugin.yml

... instead of out folder
Actually, out folder shall purely disappear from basic settings.

if a string is provided instead of an object, this will be the repo remote URL

Should be part of base plugin, since loadme task needs Jinja templates, while nmk doesn't, so it shouldn't be an nmk dependecy.
And base plugin shall not depend from python plugin.

Overriding a task has to be supported.
Handle all properties case by case...

... into usable http:// URLs

Refs using the pip://xxx syntax shall be supported, to handle project files bundled in installed python modules.
If module is not installed, pip install shall be triggered (this supposes to refactor some of the pip logic from nmk-base in the core nmk project)

Add documentation about tasks definition and build behavior

Base plugin shall handle output directory config and clean task

Define task model + handle task build

To identify root folder (parent of venv) and project folder (the one containing the initial project file)

Add deepclean task in base plugin (git clean -fdX)

... i.e. ignore input vs output computing to check if task needs to be rebuilt

Just to check that the raised error is meaningful

... to write down all the concepts somewhere...

in order to support it from venv

Add a task to setup bootstrap (loadme) scripts for Windows and Linux

Well, just do it...

well, just let's do it!

Tasks may have "unless" and/or "onlyIf" attributes, to skip the task if conditions are not met

for empty inputs/outputs/params

Add documentation on how to install nmk

• allow dotted vars resolution for dicts

Base plugin shall provide some metatasks to which other plugins will be able to register

... this should at least return 0.0.0

Add support for gitVersion config (+generated stamp file) in base plugin

on Linux: check and install if possible, point to URLs otherwise
on Windows: check and point to URLS if missing

When project hooks code in the build definition (e.g. config resolver), it shall be able to extend the Python path to directories out of the installed venv Python modules

Add a task to generate setup.cfg and setup.py files.

Add comments for better nmk API documentation

Add a task able to maintain gitignore file with usually ignored files

... instead of required config

Tasks emoji shall be a rich-interpreted string, allowing to combine several of them, and/or handle narrow ones

Add a task to compute python version from git version

To do as soon as nmk will be published on pypi!

... even on the command line

• "nmk version" shall display nmk + all plugins versions
• "nmk tasks" shall list all known tasks and their emoji/description
• "nmk help" shall display links to online help pages

Config items are supposed to be all known to the model, so that should be possible to add completion for them

Some tasks (typically always executed ones) may want to not display the log line

When a task has inputs, all project files shall be considered as well when computing updates for rebuild trigger

Config items declared in UPPERCASE shall be final (i.e. can't be overridden)

Check if this would be doable to support nmk install without venv
i.e. "root dir" (and more specifically ".nmk" cache dir) would have to be located in user directory ("~/.nmk")

Projects may share the venv at workspace level.
Loadme scripts shall handle it.
Loadme task shall be skipable in CI

... all in the title

Needed at least by loadme task, which generates a .bat file