syntaqxA host a cloud job's guardrails refuse is named in the refusal's status line, not only its body: `403 Forbidden by g1t guardrails: api.expo.dev is not an allowed domain`. Many tools show only the status line of a failed request. eas-cli's GraphQL client prints the reason phrase and drops a body that is not JSON, and apk prints `HTTP 403: Forbidden`, so a refused Expo call surfaced as a bare "Forbidden" followed by "GraphQL request failed", with nothing pointing at the guardrails. The refusal also carries an x-g1t-blocked-host header beside x-g1t-guardrails: blocked. Its plain-text body says where to allow the host: Allowed domains for every sandbox, or Workflow-only domains for the jobs of one workflow and environment. The guardrails and Actions guides say what a refused request shows.3039e06History
- ..
- agent_comments.rs
- authored.rs
- capture.rs
- checks.rs
- codeowners.rs
- commit_checks.rs
- compute.rs
- confidence.rs
- contributions.rs
- ghost.rs
- guardrails.rs
- inbox.rs
- labels.rs
- lib.rs
- lifecycle.rs
- memory.rs
- mentions.rs
- mergeability.rs
- messages.rs
- milestones.rs
- plans.rs
- prefetch.rs
- queue.rs
- retired.rs
- reviews.rs
- rows.rs
- rulesets.rs
- runs.rs
- settings.rs
- statuses.rs
- team_reviews.rs