Last committed December 2023 — appears to be a stale copy of OCI_Build. The inventory.yml now only contains a Windows VirtualBox Gaming host with ansible_shell_type: cmd. All playbooks target hosts: Prod, hosts: Docker, etc — groups that do not exist in this inventory. Every playbook would fail with "no hosts matched."
The repo creates confusion about which repo is authoritative.
Fix
Check if docker_update_containers.yml here should be copied to OCI_Build first (see OCI_Build issue)
Archive in Gitea: Settings → Danger Zone → Archive Repository
History is preserved but the repo is clearly marked inactive.
## Problem
Last committed December 2023 — appears to be a stale copy of OCI_Build. The `inventory.yml` now only contains a Windows VirtualBox Gaming host with `ansible_shell_type: cmd`. All playbooks target `hosts: Prod`, `hosts: Docker`, etc — groups that do not exist in this inventory. Every playbook would fail with "no hosts matched."
The repo creates confusion about which repo is authoritative.
## Fix
1. Check if `docker_update_containers.yml` here should be copied to OCI_Build first (see OCI_Build issue)
2. Archive in Gitea: **Settings → Danger Zone → Archive Repository**
History is preserved but the repo is clearly marked inactive.
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.
Problem
Last committed December 2023 — appears to be a stale copy of OCI_Build. The
inventory.ymlnow only contains a Windows VirtualBox Gaming host withansible_shell_type: cmd. All playbooks targethosts: Prod,hosts: Docker, etc — groups that do not exist in this inventory. Every playbook would fail with "no hosts matched."The repo creates confusion about which repo is authoritative.
Fix
docker_update_containers.ymlhere should be copied to OCI_Build first (see OCI_Build issue)History is preserved but the repo is clearly marked inactive.