granite-cli 0.2.0

CLI for discovering, configuring, and launching AI workflows powered by IBM Granite models.
1
2
3
4
5
6
7
8
9
10
11
## Project Practices

- Avoid adding new dependencies if an existing dependency or standard library could serve the same function
- Use the minimal visibility scoping for every function (only `pub` if necessary, crate-pub unless full pub necessary)
- When laying out a source file, organize it as follows:
    1. `use` directives
    2. Public functions/structs/enums/etc (mark with `/*-- public --*/` to begin section)
    3. Private functions/structs/enums/etc (mark with `/*-- private --*/` to begin seciton)
    4. Tests (mark with `/*-- tests --*/` to begin seciton)
- When formatting code, use `./scripts/fmt.sh` which runs both `clippy` and `fmt` with the right versions of the rust toolchain via `rustup`
- When writing unit tests, nothing should _ever_ depend on the local environment. This includes hardware detection, existence of pre-installed binaries, internet connectivity, and anything else that could differ between development environments