github/gh-aw

Conformance Check Failure Check ID: USE-001 Severity: LOW Category: Usability Problem Description actions/setup/js/azure_devops_work_items.cjs throws numerous Error instances (input validation, HTTP failures, work-item resolution failures) but none of them use a standardized error code prefix (E\d{3}, ERROR_, or ERR_). All other safe-output handlers in the catalog reference the standardized E001-E010 error code catalog (see SEC-006), so this handler is inconsistent with the rest of the codebase and harder for callers/agents to programmatically distinguish error classes. Affected Components Files: actions/setup/js/azure_devops_work_items.cjs 🔍 Current vs Expected Behavior Current Behavior Errors are thrown as plain messages, e.g.: throw new Error("assignee must not be empty"); throw new Error(`AZURE_DEVOPS_ORG_URL must be a valid HTTPS URL`); throw new Error(`Azure DevOps ${method} request failed with HTTP ${response.status} ${response.statusText}`); Expected Behavior Error messag

Hello, I got self hosted runner on ubuntu. When I launch a pretty dumb agentic workflow: description: > validate pertinent issue. engine: copilot labels: [automation] runs-on: mine runs-on-slim: mine runner: topology: arc-dind on: issues: types: [opened, labeled] reaction: "eyes" status-comment: true permissions: contents: read issues: read pull-requests: read tools: github: toolsets: [default] bash: ["curl"] safe-outputs: add-comment: max: 1 hide-older-comments: true add-labels: allowed: - "testing" max: 1 remove-labels: allowed: - "testing" max: 1 data: true threat-detection: false --- # issue validator Asses if a newly opened issue is for testing purposes or not. If it is, add a label "testing". In all situations, add a comment "reviewed by issue-filter workflow". Without the node topoligy 'arc-dind' there is an issue (need a glibc not a musl lib) linked to the docker dind beeing alpine (docker pr

Description Schema Consistency Checker's 2026-08-31 report (discussion #57357) found two schema-description gaps distinct from prior closures (#54179/#54400 covered docs/frontmatter.md, not main_workflow_schema.json; #54456 added tracker-id's minLength/maxLength/pattern constraints, which are already present, but not the behavior description): redirect's schema description (main_workflow_schema.json — currently: "Optional workflow location redirect for updates... When present, update follows this location and rewrites source.") only describes it as an update-location pointer. It doesn't mention that redirect: + a missing on: field is a special compile-time placeholder that gh aw compile skips with an informational message rather than compiling a runnable workflow (pkg/workflow/compiler_orchestrator_workflow.go:70, pkg/workflow/compiler_string_api.go:100-103) — a behavior already documented in docs/reference/frontmatter.md:713-718 but missing from the schema text. tracker-id's sche

Description Documentation Noob Tester's 2026-08-31 report (discussion #57338) — a fresh first-time-user pass over /gh-aw/, /gh-aw/setup/quick-start/, /gh-aw/setup/cli/ — found 3 concrete "quick win" friction points, all confirmed still live in docs/src/content/docs/setup/quick-start.mdx: The "if you already have GitHub Copilot, start there" hint (line 71, Prerequisites) isn't repeated near the 5-tab auth section (<Tabs> at line 120), so a beginner scanning just the auth tabs has no in-context steer among Copilot/Claude/Codex/Gemini/Pi. "frontmatter" and "lock file" aren't re-linked to their reference pages when they reappear in Step 4, even though each is defined once earlier. Line 114 still says the workflow file is added "either by direct push or a pull request" with no explanation of when each happens or how the user can tell which occurred. These are distinct from previously-closed doc-friction issues #55966 (fallback-path clarity, add-wizard vs add naming) and #56578 (step o

Description Daily Compiler Quality Check's 2026-08-31 rotation (discussion #57324) scored pkg/workflow/compiler_safe_outputs_builder.go 69/100 (lowest of the batch, "Acceptable" tier): the file has no dedicated _test.go file covering marshalSafeOutputsConfig/sanitizeAgentSafeOutputsConfig, and zero fmt.Errorf/%w wraps — marshalSafeOutputsConfig propagates raw marshal errors without any context about which config failed to serialize. Expected Impact Adds regression coverage for safe-outputs config marshaling/sanitization (currently untested) and gives marshal failures actionable context (which safe-output type/field failed), rather than a bare JSON-library error. Suggested Agent General-purpose Go agent — add compiler_safe_outputs_builder_test.go covering marshalSafeOutputsConfig and sanitizeAgentSafeOutputsConfig, and wrap marshal error returns with fmt.Errorf("...: %w", err). Estimated Effort Quick (~2 hours, per the source report's own estimate) Data Source DeepReport Intelligenc