Simone 385eaca98b fix(tools): run the publish guard as the committing user, not ci-runner ...

Documented with `sudo -u ci-runner`, copied from the neighbouring tools that
call the Gitea API. Wrong here: the guard fetches, fetching writes
.git/FETCH_HEAD, and that file belongs to the committing user -- so as
ci-runner it died with "impossibile aprire '.git/FETCH_HEAD': Permesso negato"
before comparing anything.

A guard that cannot run is worse than no guard, since the failure looks like
infrastructure noise rather than an answer. The question it asks is "does what
I have match what is published", so it belongs to whoever holds the working
tree.

2026-07-22 20:38:32 +02:00

..

ci-action-published.py

fix(tools): run the publish guard as the committing user, not ci-runner

2026-07-22 20:38:32 +02:00

ci-cred-check.py

feat: update action.yml to use pwsh shell and enhance vm.py with start option; add credential management scripts

2026-05-21 00:11:20 +02:00

ci-cred-set.py

feat: update action.yml to use pwsh shell and enhance vm.py with start option; add credential management scripts

2026-05-21 00:11:20 +02:00

gitea-runner-list.py

feat(runner): dedicated rust-build runner instance for LinuxRust2404

2026-07-22 14:09:22 +02:00

gitea-runner-token.py

feat(runner): dedicated rust-build runner instance for LinuxRust2404

2026-07-22 14:09:22 +02:00

graph_query.py

chore(tools): add graph_query.py dev utility under tools/

2026-05-23 19:50:21 +02:00