Skip to content

[aw] Evergreen failed #419

Description

@github-actions

Workflow Failure

Workflow: Evergreen
Branch: main
Run: https://github.com/githubnext/tsb/actions/runs/29070071260

🛡️ Protected Files: The code push was refused because the patch modifies protected files (package manifests, agent instruction files, or repository security configuration). This protection guards against unintended supply chain changes.

Blocked Operations:

  • push_to_pull_request_branch: Cannot push to pull request branch: patch modifies protected files (.github/workflows/agentics-maintenance.yml, .github/workflows/ci-doctor.lock.yml, .github/workflows/evergreen-trigger.yml, .github/workflows/evergreen.lock.yml, .github/workflows/evergreen.md, .github/workflows/shared/evergreen/ci-activation.md, .github/workflows/shared/evergreen/quota-policy.md, .github/workflows/shared/evergreen/repo-policy.md, .github/workflows/shared/evergreen/report-template.md, .github/workflows/shared/evergreen/state-labels.md, .github/workflows/shared/skills/attempt-memory-writer.md, .github/workflows/shared/skills/ci-gate-evaluator.md, .github/workflows/shared/skills/ci-log-parser.md, .github/workflows/shared/skills/ci-run-deduper.md, .github/workflows/shared/skills/deterministic-repair.md, .github/workflows/shared/skills/diff-risk-map.md, .github/workflows/shared/skills/merge-blocker-comment-reader.md, .github/workflows/shared/skills/merge-gate-reporter.md, .github/workflows/shared/skills/playground-e2e-diagnoser.md, .github/workflows/shared/skills/pr-intake.md, .github/workflows/shared/skills/repo-memory-reader.md, .github/workflows/shared/skills/safe-output-verifier.md, .github/aw/actions-lock.json, .github/workflows/shared/evergreen/labels.md, .github/workflows/shared/evergreen/memory-policy.md, .github/workflows/shared/evergreen/orchestrator-policy.md, .github/workflows/shared/evergreen/safe-output-policy.md, .github/workflows/shared/skills/api-contract-gate-repair.md, .github/workflows/shared/skills/autoloop-coordinator.md, .github/workflows/shared/skills/data-migration-gate-repair.md, .github/workflows/shared/skills/dependency-gate-repair.md, .github/workflows/shared/skills/docs-release-gate-repair.md, .github/workflows/shared/skills/frontend-e2e-repair.md, .github/workflows/shared/skills/infra-ci-repair.md, .github/workflows/shared/skills/lint-policy-review.md, .github/workflows/shared/skills/performance-gate-repair.md, .github/workflows/shared/skills/security-gate-repair.md). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.
⚙️ Configure protected-files: fallback-to-issue
safe-outputs:
  push-to-pull-request-branch:
    protected-files: fallback-to-issue

Warning

Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

  • push_to_pull_request_branch returned "success" on both attempts but GitHub branch head SHA remains e9f7ad2. Lint fixes (series.ts useLiteralKeys, timestamp.ts cognitive complexity + top-level regex) and merge of main were committed locally but did not land on the remote branch. Verification via GitHub list_commits API confirmed the branch was not updated after either push attempt.

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/tsb/actions/runs/29070071260
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

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:

safe-outputs:
  report-failure-as-issue: false

Generated from Evergreen · 546.8 AIC ·

  • expires on Jul 17, 2026, 5:04 AM UTC

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions