Azure migration Phase 4.7: dev CI deploys from the Azure runner to /opt/sapl/dev; registry moves to git.ai-automation-hub.tech. Secrets REGISTRY_TOKEN + RELEASE_PUBLISH_TOKEN already on repo. No CI runs on PRs by design (#2042) — validated by manual dry-run + post-merge pipeline watch.
Azure migration Phase 4.7: dev CI deploys from the Azure runner to /opt/sapl/dev; registry moves to git.ai-automation-hub.tech. Secrets REGISTRY_TOKEN + RELEASE_PUBLISH_TOKEN already on repo. No CI runs on PRs by design (#2042) — validated by manual dry-run + post-merge pipeline watch.
- Registry host gitea.* -> git.* (backend base FROM, frontend image,
build scripts, base workflow)
- deploy-dev: run on the Azure VM host (/opt/sapl/dev, secrets-based
registry auth, hermes-owned checkout preserved)
- build-base-image: token via REGISTRY_TOKEN secret, clone from git.
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.
Azure migration Phase 4.7: dev CI deploys from the Azure runner to /opt/sapl/dev; registry moves to git.ai-automation-hub.tech. Secrets REGISTRY_TOKEN + RELEASE_PUBLISH_TOKEN already on repo. No CI runs on PRs by design (#2042) — validated by manual dry-run + post-merge pipeline watch.