Files
clan-core/pkgs/clan-cli
a-kenji 08e2048eeb pkgs/lib: verbose git commits
Make sure the user knowns that a git command is run.

From the issue #4588:
> It is confusing at times, when executing some CLI command, expecting change,
then checking git status but no changes are observed.

We now log:
- git add (debug)
- git commit (info)

The git commit information is formatted the following way:
```
Committed machines/backup-target to git
```

Alternatives:
Currently this shows to the user what happened.
But we might want to show the user what is being run.
We could print the information before invoking the `git commit` itself.
Informing the user of a potential password input window.

Closes #4588
2025-10-01 11:46:01 +02:00
..
2024-08-02 18:56:53 +02:00
2025-10-01 11:46:01 +02:00
2025-08-26 14:48:20 +02:00
2025-08-26 16:21:15 +02:00
2025-08-26 11:36:38 +02:00
2025-09-16 19:16:53 +07:00
2025-09-16 16:37:41 +07:00
2025-08-19 15:28:25 +02:00
2025-08-08 15:28:37 +10:00

clan-cli

The Clan CLI contains the command line interface.

Hacking on the CLI

We recommend setting up direnv to load the development with Nix. If you do not have it set up you can also use nix develop directly like this:

use flake .#clan-cli --builders ''

After you can use the local bin wrapper to test things in the CLI:

./bin/clan

Run locally single-threaded for debugging

By default tests run in parallel using pytest-parallel. pytest-parallel however breaks breakpoint(). To disable it, use this:

pytest -n0 -s

You can also run a single test like this:

pytest -n0 -s tests/test_secrets_cli.py::test_users

Run all checks in a sandbox

nix build .#checks.x86_64-linux.clan-pytest-with-core
nix build .#checks.x86_64-linux.clan-pytest-without-core