Skip to content

[shared-ci] netlify/hivecommons-docs/deploy-preview failing across hivecommons/docs #527

Closed

Description

@hivecommons-hive

Every Netlify deploy for the hivecommons-docs site — deploy previews and the main production deploy — now ends in state: error with skipped: true within ~2 seconds of creation, i.e. the build never starts. This fails netlify/hivecommons-docs/deploy-preview, Pages changed, Header rules and Redirect rules on every open PR. The checks are not required (#521 and #522 merged with the same red set), but each PR shows as UNSTABLE and the production docs site is no longer being redeployed.

Evidence (public Netlify API, GET /api/v1/sites/34e6d1e2-97c1-43e3-934f-393f1be7092c/deploys):

A skipped-then-errored deploy with no build time is a site/account condition (build minutes or credits exhausted, builds paused, site locked, or a broken build settings/webhook change), not anything in the repository diff. The GitHub Actions Lint and build / TypeScript & ESLint jobs on the same heads are green, so the Docusaurus build itself is fine.

What is needed (owner-only — the hive has no Netlify access): open https://app.netlify.com/projects/hivecommons-docs/deploys, read the reason on the latest errored deploy, and either (A) restore builds (top up credits / unpause / fix build settings) or (B) if Netlify is being retired, remove the Netlify GitHub app so the four stale contexts stop being posted on PRs. Options A/B above are the decision; the hive defers Netlify-related repair on affected PRs until this closes.

Risk: credentials/infra (owner-only Netlify account)

Affected PRs so far: #521 (merged), #522 (merged), #526.

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Activity

  1. added
    ciCreated by Hive for agent-filed issue provenance
    agent/scannerCreated by Hive for agent-filed issue provenance
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Oct 30, 2026
  2. hivecommons-hive commented on Oct 30, 2026

    @hivecommons-hive
    ContributorAuthor

    What to reply

    • /hive approve: go with the recommendation
    • /hive decision <your instructions>: go ahead, following your instructions
    • /hive help: show these again

    If what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply /fixed to close it as completed; Hive clears its park labels.

    Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

  3. clubanderson commented on Nov 2, 2026

    @clubanderson
    Member

    /hive decision Choose A: retain Netlify and restore production builds and deploy previews; do not retire the service or remove its GitHub integration. Diagnose the exact account/site rejection using authorized Netlify access, then restore the existing configuration or included allowance. This authorizes no paid top-up, plan upgrade, new recurring charge, or credential disclosure. If billing or missing account access is the blocker, report the exact owner action once and retain that explicit blocker rather than generating PR-local fixes or repeated retries. Keep this incident open until a fresh main deployment and a representative preview actually reach ready; green GitHub builds alone do not resolve it.

  4. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 2, 2026
  5. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    Un-parked by @clubanderson. Decision: Choose A: retain Netlify and restore production builds and deploy previews; do not retire the service or remove its GitHub integration. Diagnose the exact account/site rejection using authorized Netlify access, then restore the existing configuration or included allowance. This authorizes no paid top-up, plan upgrade, new recurring charge, or credential disclosure. If billing or missing account access is the blocker, report the exact owner action once and retain that explicit blocker rather than generating PR-local fixes or repeated retries. Keep this incident open until a fresh main deployment and a representative preview actually reach ready; green GitHub builds alone do not resolve it.

    stage/045-needs-decision is cleared when present and approved-direction is applied; any hold label is left exactly as it was.

  6. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

  7. 1 remaining item

  8. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    🔓 Claim by @thatguywob released (lease revoked).

  9. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    🔒 Claimed by @mrbobbytables (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

  10. mrbobbytables commented on Nov 2, 2026

    @mrbobbytables
    Contributor

    Recovery evidence is now available from the public Netlify API; no repository-local repair PR is needed:

    • Production main deployment 6ae89967f19a0fc51730a0a1, commit 16350ec4ea902e14fdeb3d696f50cb59ef5eafde (verified on upstream/main), reached state: ready and was published at 2026-11-02 14:10:00 UTC.
    • Representative PR docs(runbooks): add a postmortem template #589 preview 6ae85e616f975cfc96a93b02, commit c9b88aca019898776e8d06c26cb2bab58e0e5ba4, reached state: ready at 2026-11-02 09:58:20 UTC. Both deploy summaries report successful redirect/header processing and function deployment.
    • The subsequent docs(runbooks): add a postmortem template #589 preview attempt reports error in the deploy API, but its GitHub deploy-preview status is SUCCESS, with the three associated checks NEUTRAL. Its branch now matches the documented preview-ignore rule; an API error state alone is not evidence that the site/account still rejects all builds.

    These are actual successful Netlify deployments, not merely green GitHub builds, satisfying the requested production-plus-representative-preview recovery evidence. I cannot establish the historical account rejection or what restored service from public metadata: error_message is null, and no authorized Netlify account session is available here. No credentials, billing, integration, or site configuration were changed, and no speculative code fix or retry was made.

    — hive: backend=copilot model=gpt-5.6-luna-utility


    🐝 Hive Agent: contributor | SHA: unknown

  11. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed
    stage/020-claimedClaimed by the scanner or a relay contributor
    on Nov 2, 2026
  12. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    🔓 Claim by @mrbobbytables released (lease revoked).

  13. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Nov 2, 2026
  14. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    Fixed by #589 (merged fc5488e). Closing. Reply /reopen if the problem persists.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/scannerCreated by Hive for agent-filed issue provenanceapproved-directionciCreated by Hive for agent-filed issue provenance

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions