Skip to content

[Fleet Monitor] petry-projects/google-app-scripts β€” .github/workflows/ci.ymlΒ #621

Closed

Description

@don-petry

🟑 WARNING: petry-projects/google-app-scripts / .github/workflows/ci.yml

Metric Value
Failure Rate 11.1% (1 / 9 runs)
Status WARNING
p50 Duration 66s
p95 Duration 115s
Successful Runs 8
Cancelled Runs 0

Workflow: .github/workflows/ci.yml

Last updated by Fleet Monitor run on 2026-10-13.
Threshold: failure rate > 10% over the monitored window.

Activity

  1. don-petry commented on Oct 11, 2026

    @don-petry
    CollaboratorAuthor

    Dev-Lead Implementation Plan

    Issue: #621 β€” [Fleet Monitor] petry-projects/google-app-scripts β€” .github/workflows/ci.yml

    Root cause

    Every recent CI failure (runs 38110427634, 37966969759, 37964678067, 37965467704) is in the autofix job on standards-sync/workflows-* PRs. The sync adds the standards-owned caller stub .github/workflows/persona-mention.yml. Prettier reformats it: it collapses the two-space gap before # NOSONAR and reflows the contents: read # ... comment block. Then the autofix push is rejected:

    ! [remote rejected] ... (refusing to allow a GitHub App to create or update workflow `.github/workflows/persona-mention.yml` without `workflows` permission)
    

    Even if the push had worked, reformatting would add byte-drift against the central stub-drift guard. That's the same problem already solved for dev-lead.yml, agent-shield.yml, pr-auto-review.yml, etc.

    Scope

    Add .github/workflows/persona-mention.yml to .prettierignore, with the same rationale comment used for the other verbatim standards stubs.

    Implementation Checklist

    • .prettierignore: add a persona-mention.yml entry with a justification comment

    Tests to Write

    • None. This is a configuration-only change with no runtime behavior (TDD exception). It is checked by npx prettier --check against the synced stub content.

    Test Command

    npm run check and npm test

  2. don-petry commented on Oct 16, 2026

    @don-petry
    CollaboratorAuthor

    βœ… Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-10-13 (3 days) β€” the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions