githubnext / githubnext/gh-aw-wizard
[aw] Primer Branding reported incomplete result
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 3h 8m
- Merged PRs (30d)
- 244
Description
### Workflow Failure
**Workflow:** [Primer Branding](https://github.com/githubnext/gh-aw-wizard/blob/main/.github/workflows/primer-branding.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-wizard/actions/runs/33463263999
> [!WARNING]
> **Task Could Not Be Completed**: The agent reported that the task could not be performed due to an infrastructure or tool failure.
**Reasons:**
- Found one on-brand fix (hardcoded orange rgba(255,112,67) in .landing-glow gradient replaced with a Primer orange-scale-derived CSS variable), but npm test fails on main HEAD itself (6 pre-existing workflow.test.js assertion failures unrelated to styling) before any of my edits. Workflow rules forbid opening a PR when tests fail, so I reverted the CSS change and cannot submit it.
Verified via `git stash` that the same 6 test failures occur on unmodified main (test/workflow.test.js, generateAgentPrompt suite: boundary-constraint, duplicate-prevention, skip-if-match schema, max/expires, protected-files, PR-spam assertions all fail — actual output is a generic "Create a draft PR..." string instead of expected guidance text, indicating a pre-existing bug/regression in src/js/workflow.js or its data, not caused by CSS).
Primer-brand audit findings (not blocked by test issue, for reference):
- src/styles/style.css line ~1557: `.landing-glow` radial-gradient used a bare hardcoded `rgba(255, 112, 67, 0.24)` for the "warm" glow stop, while its sibling stops in the same gradient correctly reference CSS custom properties (`--accent-blue-rgb`, `--accent-green-rgb`). Fix: added `--thermo-warm-rgb: 240, 138, 58` (derived from Primer's `--base-color-scale-orange-3` = #f08a3a) and referenced it via `rgba(var(--thermo-warm-rgb), 0.24)`, matching the site's existing token-driven pattern. This was reverted since it could not be shipped as a PR under the test-gate rule.
- No other significant deviations found: color variables elsewhere already fall back to Primer color tokens (`--color-canvas-default`, `--color-fg-default`, etc.), typography uses system font stacks consistent with Primer's brand type approach for lightweight sites, and spacing uses rem-based scale consistently.
Recommend a maintainer first fix the pre-existing test/workflow.test.js failures (unrelated to this workflow's scope) before this branding pass can produce a mergeable PR.
This is a structured incompletion signal (`report_incomplete`), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-wizard/actions/runs/33463263999
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow primer-branding failure in https://github.com/githubnext/gh-aw-wizard/actions/runs/33463263999`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [Primer Branding](https://github.com/githubnext/gh-aw-wizard/actions/runs/33463263999) · 43 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-wizard+is%3Aissue+%22gh-aw-workflow-id%3A+primer-branding%22&type=issues)
> - [x] expires on Sep 8, 2026, 2:44 AM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running npm test and reviewing the six failing assertions in test/workflow.test.js, then trace the generated guidance through src/js/workflow.js and its related data. Done means the pre-existing workflow test failures are resolved, the full test suite passes, and the Primer Branding workflow can produce a mergeable result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100