Auto-recovery snapshot of shard auto-04d3624a from image auto-04d3624a-34caac15-6fd59898-920249ec-afc2de34. Fossil branch. The commit's content already landed in admin/brencher:main via PR #28 (closed) and is part of PR #11 family. Opening this PR is for archival/reference only; mergeable will likely be False because the content is already in main.
Auto-recovery snapshot of shard auto-04d3624a from image auto-04d3624a-34caac15-6fd59898-920249ec-afc2de34. Fossil branch. The commit's content already landed in admin/brencher:main via PR #28 (closed) and is part of PR #11 family. Opening this PR is for archival/reference only; mergeable will likely be False because the content is already in main.
admin
changed target branch from main to main_rec2026-09-06 16:27:02 +02:00
Migrates backend/configs/hermes.py from the legacy single-remote
url= form to the remotes=[{name, url}, ...] form introduced by #3.
The deploy target is admin/ansible (compose at poc/hermes/stack-compose.yml),
not uber_backup as the old URL string suggested. Mirrors the pattern in
backend/configs/hermes_infra.py after PR #8:
- gitea_hermes: where feature branches live (hermes/ansible:*)
- gitea_admin: the live-deploy source (admin/ansible:*)
No github remote: brencher container cannot reach github through the
proxy (HTTP 403 on CONNECT tunnel; see #23 for the same fix).
branchNamePrefix='ansible' is dropped — it's a no-op when no remote
is named 'origin' (backend/steps/git.py ~L104).
Closes#21
Refs #11 (parallel issue, same scope)
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.
Auto-recovery snapshot of shard auto-04d3624a from image auto-04d3624a-34caac15-6fd59898-920249ec-afc2de34. Fossil branch. The commit's content already landed in admin/brencher:main via PR #28 (closed) and is part of PR #11 family. Opening this PR is for archival/reference only; mergeable will likely be False because the content is already in main.
Migrates backend/configs/hermes.py from the legacy single-remote url= form to the remotes=[{name, url}, ...] form introduced by #3. The deploy target is admin/ansible (compose at poc/hermes/stack-compose.yml), not uber_backup as the old URL string suggested. Mirrors the pattern in backend/configs/hermes_infra.py after PR #8: - gitea_hermes: where feature branches live (hermes/ansible:*) - gitea_admin: the live-deploy source (admin/ansible:*) No github remote: brencher container cannot reach github through the proxy (HTTP 403 on CONNECT tunnel; see #23 for the same fix). branchNamePrefix='ansible' is dropped — it's a no-op when no remote is named 'origin' (backend/steps/git.py ~L104). Closes #21 Refs #11 (parallel issue, same scope)