konairius/homelab
10
0
Fork 0
Code Issues 8 Pull Requests 2 Packages Projects Releases 1 Wiki Activity

docs: konairius/homelab on main in runbooks and READMEs #1380

Merged
k.renner merged 1 commits from claude/docs-konairius-main into main 2026-10-19 09:25:52 +00:00
Conversation 1 Commits 1 Files Changed 5
+21 -21
claude-bot commented 2026-10-19 09:20:39 +00:00
Member
Copy Link
Copy Source

Task 7 of the homelab → konairius plan.

  • RUNBOOK-cold-rebuild.md: repo konairius/homelab (it still said gitea_admin/homelab), branch main, including flux bootstrap --branch=main and the GitHub mirror check.
  • RUNBOOK-home-assistant-image-rollback.md, README.md, image-automation/README.md: main. The past lidarr incident line stays as written.
  • Plan Task 6 now records what Cut-over 2 actually needed: patching the live GitRepository ref.branch (Flux can't fetch the commit that changes its branch once master is gone), cron updates via the API (woodpecker-cli 3.18.0 returns 404 against server 3.19.0), and the seventh cron uptime-kuma-token-renew.

Dated plans/specs and MIGRATION* history unchanged.

🤖 Generated with Claude Code

Task 7 of the homelab → konairius plan. - `RUNBOOK-cold-rebuild.md`: repo `konairius/homelab` (it still said `gitea_admin/homelab`), branch `main`, including `flux bootstrap --branch=main` and the GitHub mirror check. - `RUNBOOK-home-assistant-image-rollback.md`, `README.md`, `image-automation/README.md`: `main`. The past lidarr incident line stays as written. - Plan Task 6 now records what Cut-over 2 actually needed: patching the live GitRepository `ref.branch` (Flux can't fetch the commit that changes its branch once `master` is gone), cron updates via the API (woodpecker-cli 3.18.0 returns 404 against server 3.19.0), and the seventh cron `uptime-kuma-token-renew`. Dated plans/specs and `MIGRATION*` history unchanged. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude-bot added 1 commit 2026-10-19 09:20:39 +00:00
docs: konairius/homelab on main in runbooks and READMEs
ci/woodpecker/pr/ci-scripts-test Pipeline was successful
Details
review-bot reviewed: comment
Details
ci/woodpecker/pr/ci-manifests-test Pipeline was successful
Details
cdf0b5ffca 
Cold-rebuild and HA-rollback runbooks, README and the image-automation README
name main and konairius/homelab. The plan records the Flux ref patch and the
cron API calls Cut-over 2 needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
review-bot left a comment
Member
Copy Link
Copy Source

🤖 Automated review — model claude-haiku-5-5, commit cdf0b5ffca7f7189c8d08c1e70df6f8a45a727b1.

Automated review by the review-bot: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review.

Summary

This docs-only PR (5 files, +21/−21) changes the runbooks and READMEs from gitea_admin/homelab and master to konairius/homelab and main, and rewrites Task 6 of a dated plan to record what the cut-over needed. The new text matches the live config I could read: gotk-sync.yaml has ref.branch: main and the konairius/homelab URL, update-automation.yaml pushes to main, and bootstrap.sh defaults FLUX_BRANCH to main. The change is not already on main (the base still says master), no other open PR touches these four doc files, and the PR is mergeable.

⚪ Unverified

  • Mirror state. kubernetes/RUNBOOK-cold-rebuild.md:39-42, :56-60 and :409-419 say Gitea's native push-mirror on konairius/homelab keeps github.com/konairius/Homelab at main. I have no tool that reads push-mirror settings or GitHub, so this is unchecked. The plan's Task 6 Step 10 (docs/superpowers/plans/2026-10-18-homelab-konairius-main.md, head line 121) says the GitHub default branch and master still need handling, so the mirror may not match the runbook yet.
  • Live Woodpecker and version facts in the plan. Plan Step 5 (:116) gives cron ids and says woodpecker-cli 3.18.0 returns 404 against server 3.19.0. I confirmed the uptime-kuma-token-renew cron exists (.woodpecker/deploy-uptime-kuma.yml:12). I did not check the other ids or the 404 claim. The image-automation README (kubernetes/infrastructure/image-automation/README.md:79-84) says the CLI must track the server, so if the 3.18 vs 3.19 skew is real, the pinned CLI in the pipeline may be stale. I did not check the pin.
  • Sweep completeness. CONTRIBUTING.md is clean. kubernetes/RECOVERY.md and kubernetes/RUNBOOK-baremetal-conversion.md came back base64-encoded and I could not scan them reliably for master or k.renner/homelab. They are outside this PR's stated scope.

🟡 Suggestions

  • Dated plan edited against its own rule. The PR body says "Dated plans/specs and MIGRATION* history unchanged", and the plan's Task 7 (docs/superpowers/plans/2026-10-18-homelab-konairius-main.md:127) says "Leave dated plans/specs ... unchanged". This PR still rewrites Task 6 Steps 4–5 in that dated plan (:115-116). Either keep the plan as written and record the live findings elsewhere, or correct the PR body.
  • Shared plan file with open PR #1373. #1373 (claude/plan-step0-claude-bot) also edits this plan file, in its Task 3 hunk. The hunks look separate and both PRs report mergeable, but whichever merges second should be re-checked for conflicts.

Tests

Not applicable: docs-only, and there is no test suite for runbook prose. The commands in the runbooks (git ls-remote ... main, the kubectl patch, git log origin/main) were not run.

Recommendation

Looks reasonable — no blocking issues; comments above are optional.

🤖 **Automated review** — model `claude-haiku-5-5`, commit `cdf0b5ffca7f7189c8d08c1e70df6f8a45a727b1`. > Automated review by the `review-bot`: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review. --- ## Summary This docs-only PR (5 files, +21/−21) changes the runbooks and READMEs from `gitea_admin/homelab` and `master` to `konairius/homelab` and `main`, and rewrites Task 6 of a dated plan to record what the cut-over needed. The new text matches the live config I could read: `gotk-sync.yaml` has `ref.branch: main` and the `konairius/homelab` URL, `update-automation.yaml` pushes to `main`, and `bootstrap.sh` defaults `FLUX_BRANCH` to `main`. The change is not already on `main` (the base still says `master`), no other open PR touches these four doc files, and the PR is mergeable. ## ⚪ Unverified - **Mirror state.** `kubernetes/RUNBOOK-cold-rebuild.md:39-42`, `:56-60` and `:409-419` say Gitea's native push-mirror on `konairius/homelab` keeps `github.com/konairius/Homelab` at `main`. I have no tool that reads push-mirror settings or GitHub, so this is unchecked. The plan's Task 6 Step 10 (`docs/superpowers/plans/2026-10-18-homelab-konairius-main.md`, head line 121) says the GitHub default branch and `master` still need handling, so the mirror may not match the runbook yet. - **Live Woodpecker and version facts in the plan.** Plan Step 5 (`:116`) gives cron ids and says `woodpecker-cli` 3.18.0 returns 404 against server 3.19.0. I confirmed the `uptime-kuma-token-renew` cron exists (`.woodpecker/deploy-uptime-kuma.yml:12`). I did not check the other ids or the 404 claim. The image-automation README (`kubernetes/infrastructure/image-automation/README.md:79-84`) says the CLI must track the server, so if the 3.18 vs 3.19 skew is real, the pinned CLI in the pipeline may be stale. I did not check the pin. - **Sweep completeness.** `CONTRIBUTING.md` is clean. `kubernetes/RECOVERY.md` and `kubernetes/RUNBOOK-baremetal-conversion.md` came back base64-encoded and I could not scan them reliably for `master` or `k.renner/homelab`. They are outside this PR's stated scope. ## 🟡 Suggestions - **Dated plan edited against its own rule.** The PR body says "Dated plans/specs and `MIGRATION*` history unchanged", and the plan's Task 7 (`docs/superpowers/plans/2026-10-18-homelab-konairius-main.md:127`) says "Leave dated plans/specs ... unchanged". This PR still rewrites Task 6 Steps 4–5 in that dated plan (`:115-116`). Either keep the plan as written and record the live findings elsewhere, or correct the PR body. - **Shared plan file with open PR #1373.** #1373 (`claude/plan-step0-claude-bot`) also edits this plan file, in its Task 3 hunk. The hunks look separate and both PRs report mergeable, but whichever merges second should be re-checked for conflicts. ## Tests Not applicable: docs-only, and there is no test suite for runbook prose. The commands in the runbooks (`git ls-remote ... main`, the `kubectl patch`, `git log origin/main`) were not run. ## Recommendation Looks reasonable — no blocking issues; comments above are optional. <!-- pr-review:sha=cdf0b5ffca7f7189c8d08c1e70df6f8a45a727b1 -->
k.renner merged commit 2b2fd3647b into main 2026-10-19 09:25:52 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
review-bot
Labels
Clear labels
apollo
Hermes expert: Immich, Audiobookshelf, Libation, Navidrome, Music Assistant
 atlas
Hermes expert: Talos, Flux, network, Authentik, Matrix, monitoring
 clio
Hermes expert: Paperless, wiki, ical-proxy, TRMNL, websites
 daedalus
Hermes expert: Gitea, Woodpecker, Renovate, review-bot, Hermes
 hestia
Hermes expert: Home Assistant, IoT, MQTT, ESPHome, voice
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
alert-monitor-bot claude-bot (Claude Bot) flux hermes-bot issue-fix-bot k.renner renovate-bot review-bot (Review Bot) security-bot update-audit-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: konairius/homelab#1380