githubnext / githubnext/gh-aw-cao
[self-care:open-source-failures] Investigate shared activation artifact upload failures in githubnext/gh-aw-workshop
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
Multiple `githubnext/gh-aw-workshop` workflows are failing at the same activation step, `Upload activation artifact`, which points to a shared activation-path defect rather than isolated workflow logic problems. In the bounded 7-day snapshot, 5 runs across 5 workflows hit the same step failure.
**Action:** The `githubnext/gh-aw-workshop` maintainers should investigate the shared activation artifact upload path and restore one representative workflow first; accept when a rerun of at least one cited workflow completes the activation job past `Upload activation artifact` and subsequent scheduled runs stop repeating this signature.
Agent prompt
Investigate why activation jobs in `githubnext/gh-aw-workshop` fail at `Upload activation artifact` across multiple workflows. Check the shared activation logic, artifact naming and paths, retention settings, and any recent workflow-source or runtime changes affecting artifact upload. Implement the smallest safe fix, validate it with the narrowest relevant checks, and summarize the root cause and how it was verified.
Critical findings:
- Severity: P1 because the same actionable signature appears in at least two runs.
- Representative run: https://github.com/githubnext/gh-aw-workshop/actions/runs/33952592026
- Affected workflows:
- `.github/workflows/title-similarity-review.lock.yml`
- `.github/workflows/workflow-skills-editor.lock.yml`
- `.github/workflows/workshop-author.lock.yml`
- `.github/workflows/workshop-builder.lock.yml`
- `.github/workflows/workshop-order-review.lock.yml`
- Evidence-supported cause: more evidence is required for a root cause, but the shared failing step supports a common activation artifact upload defect.
- Confidence: medium.
Representative evidence
Representative runs:
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33952592026
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33952513038
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33951208248
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33950420537
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33950041261
Observed common signature:
- Job: `activation`
- Step: `Upload activation artifact`
### Control Plane
- Correlation ID: `33956123579-210`
- Central repository: `githubnext/gh-aw-cao`
- Control-plane run: https://github.com/githubnext/gh-aw-cao/actions/runs/33956123579
> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33956300121) · pi · gpt54 · 24.9 AIC · ⌖ 8.56 AIC · ⊞ 8.3K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Fself-care-open-source-failures%22&type=issues)
> - [x] expires on Sep 19, 2026, 8:54 AM UTC
Contributor guide
Research direction
Start with the representative run 33952592026 and the activation job's `Upload activation artifact` step. Compare the shared activation logic, artifact names and paths, retention settings, and the five affected `.github/workflows/*.lock.yml` files listed in the issue. Done means a cited workflow reruns past that step and subsequent scheduled runs no longer repeat the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100