syntaqxA deploy build reads g1t's reason when a step is refused: ureq makes any status over 399 an error, so the registry step's 409 not_enabled (g1t.page runs no containers yet) failed the build as "could not report registry to g1t: status code 409" before the build could fall back to the project's site, or say Docker deployments are not switched on. Tests answer a step with a 409 and a 502.998eca2History
- ..
- access.test.ts
- access.ts
- cloudflare.ts
- containers.flow.test.ts
- containers.test.ts
- containers.ts
- custom-hostnames.ts
- domains.ts
- environments.test.ts
- environments.ts
- hostname.test.ts
- hostname.ts
- index.ts
- metering.test.ts
- metering.ts
- moves.flow.test.ts
- moves.test.ts
- moves.ts
- names.test.ts
- names.ts
- redirect.test.ts
- redirect.ts
- repo-deployments.ts
- retries.test.ts
- retries.ts
- telemetry.test.ts
- telemetry.ts
- workflow-builds.flow.test.ts
- workflow-builds.test.ts
- workflow-builds.ts