Skip to content

docs: add netlify-build-failure runbook to README Operational Readiness index - #6795

Merged
kubestellar-hive[bot] merged 1 commit into
mainfrom
operations/readme-netlify-build-failure-runbook-link
Sep 11, 2026
Merged

docs: add netlify-build-failure runbook to README Operational Readiness index#6795
kubestellar-hive[bot] merged 1 commit into
mainfrom
operations/readme-netlify-build-failure-runbook-link

Conversation

@kubestellar-hive

Copy link
Copy Markdown
Contributor

What

Adds runbooks/netlify-build-failure.md to the README's ## Operational Readiness index, next to deploy-rollback.md.

Why

Fixes #6794. The runbook was added in #6782 (and is already linked from runbooks/deploy-rollback.md), but was never added to the README's index of runbooks, so it was undiscoverable to anyone scanning the README for available runbooks during an incident (e.g. a direct-to-main Netlify build failure alerted by netlify-error-reporter.yml).

Scope check

  • Documentation-only change (one README bullet).
  • Does not touch any workflow file.
  • Does not weaken any existing alert or SLO.
  • Does not add a probe.

Closes #6794.

— hive: agent=operations backend=copilot model=claude-sonnet-4-6

…diness index

Fixes #6794. The runbook was added in #6782 but never linked from the
README's Operational Readiness list, so it was undiscoverable alongside
the other runbooks for anyone scanning the README during an incident.

Signed-off-by: kubestellar-hive[bot] <kubestellar-hive-bot@users.noreply.github.com>
@kubestellar-hive

Copy link
Copy Markdown
Contributor Author

Important

Held for human sign-off on the direction, not on the code.

This PR's only tracked rationale is #6794, which the hive filed itself — issue #6794 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117).

The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the approved-direction label — and remove the hold label here.

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Sep 7, 2026
@netlify

netlify Bot commented Sep 7, 2026

Copy link
Copy Markdown

Deploy Preview for kubestellar-docs ready!

Name Link
🔨 Latest commit 364fad2
🔍 Latest deploy log https://app.netlify.com/projects/kubestellar-docs/deploys/6a9f412306a33b0008d7a656
😎 Deploy Preview https://deploy-preview-6795--kubestellar-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@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 kproche 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

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Sep 7, 2026
@kubestellar-prow

Copy link
Copy Markdown

Hi @kubestellar-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubestellar-prow kubestellar-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 7, 2026
@clubanderson clubanderson removed the hold label Sep 11, 2026
@clubanderson

Copy link
Copy Markdown
Member

Direction acknowledged by hub admin (approved-direction added on #6794); releasing the #5117 hold. This hive runs at ACMM L6 and may act on its own findings.

@kubestellar-hive
kubestellar-hive Bot merged commit 928d4fb into main Sep 11, 2026
14 of 16 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the operations/readme-netlify-build-failure-runbook-link branch September 11, 2026 16:57
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

Check out what's new:

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey

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

Labels

copilot dco-signoff: yes Indicates the PR's author has signed the DCO. documentation Improvements or additions to documentation needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[operations] README's Operational Readiness index omits runbooks/netlify-build-failure.md

1 participant