Continues #9. .gitea/workflows/deployLibvirt.yaml has no on: trigger, so it has never run. It also installs Ansible at run time and expects deployment secrets.
Work: add workflow_dispatch only, use the tools image, target the deploy path from D4, and pin the action.
Acceptance: a dry run with --check works from the deploy runner, with Eric present.
Depends on: G1, I4, D4.
Continues #9. `.gitea/workflows/deployLibvirt.yaml` has no `on:` trigger, so it has never run. It also installs Ansible at run time and expects deployment secrets.
**Work**: add `workflow_dispatch` only, use the tools image, target the deploy path from D4, and pin the action.
**Acceptance**: a dry run with `--check` works from the deploy runner, with Eric present.
Depends on: G1, I4, D4.
claude
added this to the CI/CD 4: Continuous delivery milestone 2026-11-09 17:07:11 +00:00
claude
added the cicd label 2026-11-09 17:07:11 +00:00
claude
added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Continues #9.
.gitea/workflows/deployLibvirt.yamlhas noon:trigger, so it has never run. It also installs Ansible at run time and expects deployment secrets.Work: add
workflow_dispatchonly, use the tools image, target the deploy path from D4, and pin the action.Acceptance: a dry run with
--checkworks from the deploy runner, with Eric present.Depends on: G1, I4, D4.