Pedro Algarvio db06c6f31c Add report.ci support %!s(int64=4) %!d(string=hai) anos
..
README.md a5b9961f78 Lay the ground for `invoke` usage %!s(int64=4) %!d(string=hai) anos
__init__.py 8df140fc1f Add invoke task to generate Github Actions %!s(int64=4) %!d(string=hai) anos
docs.py dfddc15569 Resolve paths passed directly with `--files` %!s(int64=4) %!d(string=hai) anos
filemap.py e6e1ab3ef6 Add task to check `tests/filename_map.yml` validity %!s(int64=4) %!d(string=hai) anos
gha.py db06c6f31c Add report.ci support %!s(int64=4) %!d(string=hai) anos
loader.py f6c2355f33 Add loader checks although not currently enforcing them %!s(int64=4) %!d(string=hai) anos
utils.py 15b4988db7 Work around no TTY on github actions %!s(int64=4) %!d(string=hai) anos

README.md

What is this directory?

This directory contains python scripts which should be called by invoke.

Instead of having several multi-purpose python scripts scatered through multiple paths in the salt code base, we will now concentrate them under an invoke task.

Calling Invoke

Invoke can be called in the following ways.

Installed system-wide

If invoke is installed system-wide, be sure you also have blessings installed if you want coloured output, although it's not a hard requirement.

inv docs.check

Using Nox

Since salt already uses nox, and nox manages virtual environments and respective requirements, calling invoke is as simple as:

nox -e invoke -- docs.check