Skip to content

πŸ“– docs: resync the Hive docs mirror from hive@v5 - #528

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
bot/hive-docs-refresh
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
bot/hive-docs-refresh

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated daily resync of the committed mirrors under docs/content/
via npm run sync-hive-docs and npm run sync-sibling-docs.

This PR was opened with GITHUB_TOKEN, so GitHub does not start
pull_request workflows for it. The refresh run instead dispatches
Build, TypeScript & Lint Check, Vitest, npm audit, Internal Links
and Markdown Lint on the PR branch; their check-runs land on the
head SHA as usual.

Refresh run: https://github.com/hivecommons/docs/actions/runs/41014626317

Refs #496

The hive sweep merges this PR once CI is green.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@kubestellar-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify

netlify Bot commented Oct 30, 2026

Copy link
Copy Markdown

❌ Deploy Preview for hivecommons-docs failed. Why did it fail? β†’

Name Link
πŸ”¨ Latest commit c8578ee
πŸ” Latest deploy log https://app.netlify.com/projects/hivecommons-docs/deploys/6ae43a01018d96df1cba08cc

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Decision needed: @clubanderson should check the Netlify deploy log for 6ae43a01018d96df1cba08cc and decide whether the deploy-preview failure is a preview-environment problem (merge this resync) or a content regression in the mirrored v5 docs (hold it).

The repo's own checks are all green on c8578ee (Lint and build, TypeScript & ESLint, unit tests, internal links, markdownlint, DCO), but the netlify/hivecommons-docs/deploy-preview status is failure, and that drags Header rules, Pages changed and Redirect rules red with it.

What I could verify: netlify.toml runs NEXT_PUBLIC_BRANCH=${BRANCH:-main} npm run build, and package.json's build/prebuild are the same scripts the green "Lint and build" job ran on this exact head β€” so the Next build of this content succeeds in GitHub Actions. The Netlify log itself needs a site login, so I cannot tell whether the preview failed on the prebuild sync steps (network from Netlify's builder), the @netlify/plugin-nextjs step, or a page in this diff. Nothing in the 58 mirrored files is hand-written; it is the daily sync-hive-docs output.

Routing rather than judging: whoever can open the Netlify deploy log can settle this in a minute. I have not changed or closed anything.

β€” hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge:

  • the reviewer swarm returned requires_human @c8578ee
  • the review found: sensitive-paths question from the correctness review
  • reviewer question: @clubanderson should check the Netlify deploy log for 6ae43a01018d96df1cba08cc and decide whether the deploy-preview failure is a preview-environment problem (merge this resync) or a content regression in the mirrored v5 docs (hold it).
  • the automerge lane will not merge this unattended

Head: verdict requires_human @c8578ee, 6/6 checks green, DCO yes, soak 0s of 30m0s.

What to do: approve this head (c8578ee) to merge as-is, or leave a changes requested review (or reply /hive decision <what to change>) and the hive will push the fix.

How to release it:

  • After reading the verdict, a trusted merger can submit a GitHub Approve review for the current head and the lane clears the hold on its next pass; /hive approve replies on a PR are acknowledged but not consumed.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. Approval does not bypass CI, hold labels or other merge gates.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

hive/shared-ci: the three red checks here (Header rules / Pages changed / Redirect rules β€” hivecommons-docs) are the Netlify deploy fault tracked in #527, which fails instantly on main and on every PR; nothing in this mirror resync is being blamed. Deferring to that incident β€” no PR-local repair, and this PR re-runs once the Netlify site/account is fixed.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

β€” hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Closed as superseded by #497 by @clubanderson from the Hive dashboard.

Superseded by #497, which resynced the mirror for #496.

@hivecommons-hive hivecommons-hive Bot added the hive/superseded Closed by Hive: a different merged PR already landed this change label Oct 30, 2026
@hivecommons-hive hivecommons-hive Bot closed this Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes hive/superseded Closed by Hive: a different merged PR already landed this change size/XXL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants