syntaqxThe docs say how the merge queue blames a failure: a state is held while entries ahead of it are still being tested, smaller combinations narrow down which entries ahead a change breaks with within three builds, who is told and with what (the timeline, the issue, the session, an integration_failure decision and integration.failed), and that a fixed pull request rejoins the queue by itself once its checks pass. Sessions and why-blame gains decision records (their kinds and confidences, what g1t records itself, record_decision and list_decisions) and why over the API; the webhooks guide lists integration.failed, integration.passed and decision.recorded; the MCP reference, bring your own agent and llms.txt name the new actions.b548a9aHistory
- ..
- about.ts
- access.ts
- account-deletion.ts
- accounts.ts
- actions.ts
- advisories.ts
- agents.ts
- audit.ts
- billing.ts
- chat-markdown.test.ts
- chat-markdown.ts
- chat.test.ts
- chat.ts
- checks.ts
- claude-plugin.test.ts
- claude-plugin.ts
- clients.ts
- codeowners.ts
- coding-agents.test.ts
- coding-agents.ts
- compute.ts
- connectors.test.ts
- connectors.ts
- customize.test.ts
- customize.ts
- d1.test.ts
- d1.ts
- datasets.fixtures.json
- datasets.test.ts
- datasets.ts
- deploy-keys.ts
- deployments.ts
- discovery.test.ts
- discovery.ts
- docs.ts
- events.ts
- folios-dashboard.ts
- folios-design.ts
- folios-slides.ts
- folios.fixtures.json
- folios.test.ts
- folios.ts
- github.ts
- guardrails.ts
- identity.ts
- ids.test.ts
- ids.ts
- inbox.ts
- index.ts
- instances.ts
- integrations.ts
- marketplace.test.ts
- marketplace.ts
- members.ts
- names.test.ts
- names.ts
- notify.ts
- oauth.ts
- og.ts
- packages.ts
- people.ts
- platform.ts
- projects.ts
- rate-limits.ts
- repos.ts
- result.ts
- rules.ts
- runners.ts
- scopes.ts
- search.ts
- security-suite.ts
- security.ts
- skills.ts
- sounds.ts
- status.ts
- teams.ts
- telemetry.ts
- updates.ts
- webhooks.ts
- work.ts