[Plans] CI repair plans for a future session#5108
Draft
btshrewsbury-viam wants to merge 1 commit into
Draft
Conversation
Add .github/workflows/plans/: a per-issue plan set so a future session can execute each repair without re-deriving context. Each plan covers problem, root cause, prerequisites, step-by-step changes with file/line references, verification, rollback, and risks. - 00 provision a new org, machine, and secrets (maps every hardcoded ID and secret to re-point; foundation for the live-API jobs) - 01 restore failure notifications (Jira + backup alert) - 02 fix Test Code Samples (org member, step isolation, ID re-point, flaky teardown tolerance) - 03 fix Alias reminder (set-output -> GITHUB_OUTPUT) - 04 fix PR Test Label Manager (confirm safe-to-build consumer, trigger/cond) - 05 fix SDK method coverage (signal, concurrency, scraper hardening) - 06 cleanup and modernization (action bumps, dead steps, naming) Index README orders the plans and lists the secrets inventory. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viambot
added
the
safe to build
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft / reference — working plans, not necessarily for merge. A future session can execute any plan from this branch.
Adds
.github/workflows/plans/: a detailed, per-issue repair plan for the broken and degraded CI jobs identified in the workflow audit (companion to the reference doc + repair TODO in #5107).Files
README.md— index, execution order, status legend, and a repository-secrets inventory.00-provision-org-machine-secrets.md— the foundation. Create a new Viam org, location, machine, and API keys; maps every hardcoded ID (pg5q3j3h95,deb8782c…,824b6570…,1030f25a…,b5e9f350…, etc.) and every secret to re-point. Prerequisite for plan 02.01-restore-notifications.md— fix the failing Jira steps in the 3 scheduled jobs + add a backup alert (highest impact: those jobs are currently unmonitored).02-fix-test-code-snippets.md— roleless org member (ties to Fix Test Code Samples: select a non-owner member in fleet-api orgs sample #5106), split Python/Go/TS so one failure stops hiding the others, re-point IDs, tolerate flaky teardown calls, audit machine-dependent samples.03-fix-alias-reminder.md— migrate disabled::set-outputto$GITHUB_OUTPUTso the reminder posts.04-fix-pr-labeler.md— confirm thesafe to buildconsumer (likely Netlify), fix the trigger/condition mismatch and error handling.05-fix-check-methods.md— restore the signal, fix the null-PR concurrency group, correct the cron comment, harden the scrapers.06-cleanup-and-modernization.md— action-version bumps, pin moving refs, remove dead venv/deploy steps, fix misleading names, decide blocking-vs-drop for informational linters.Each plan follows the same shape: problem, root cause, prerequisites, step-by-step changes with file/line refs, verification, rollback, and risks. Per the request, the plans assume a new org, machine, and updated GitHub Action secrets.
All files pass prettier, markdownlint, and vale (error level).
🤖 Generated with Claude Code