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
- ..
- abuse.tsx
- aliases.tsx
- audit.tsx
- blocked-domains.tsx
- costs-bill.tsx
- costs.tsx
- credits.tsx
- deleted-accounts.tsx
- deleted-workspaces.tsx
- enterprise.tsx
- enterprises.tsx
- incident-new.tsx
- incident-postmortem.tsx
- incident.tsx
- incidents.tsx
- invites.tsx
- invoices.tsx
- legacy-accounts.tsx
- maintenance-new.tsx
- maintenance.tsx
- new-enterprise.tsx
- overages.tsx
- overview.tsx
- reach-out.tsx
- requests.tsx
- soon.tsx
- stripe.tsx
- timezone.tsx
- user.tsx
- velocity.tsx
- workspace-abuse.tsx
- workspace.tsx
- workspaces.tsx