Repository navigation
Reconcile the HolidayLights Registry Entry and Rollout Trackers After Its Promotion - #4055
Conversation
Delete the HolidayLights driftNote saying the 2025 and 2026 show folders and the fleet baseline wait on develop for a develop->main promotion. ptr727/HolidayLights#17 promoted them, and main now holds both show folders and the baseline. The audit flags the note because it asserts pending work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reusable-workflow and LF rollout trackers still list HolidayLights as not adopted. Its main has called the hub validate-task.yml by pin since ptr727/HolidayLights#15, and has carried the LF defaults since ptr727/HolidayLights#10, both promoted in ptr727/HolidayLights#17. The LF row also names the operational model the registry declares. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
A recorded local strict-review pass covers head |
There was a problem hiding this comment.
🔵 Needs a closer look
The registry and rollout claims rely on live ptr727/HolidayLights main state, but the configured GitHub API returned 404, preventing independent verification of those cross-repository facts.
No open issues 🎉
What changed in this PR
This pull request reconciles the HolidayLights registry and rollout trackers with its promoted main state.
Changes:
- Removes the obsolete registry note describing pending HolidayLights promotion work.
- Marks HolidayLights as adopted for the merge-bot and validation reusable workflows.
- Records its operational classification and LF conversion.
- Requires regeneration of the workflow reuse report to reflect these adoptions.
| File | Description |
|---|---|
| registry/repos.json | Removes the outdated drift note describing pending HolidayLights promotion work. |
| docs/reusable-workflows.md | Marks HolidayLights as adopted for the merge-bot and validation reusable workflows. |
| docs/eol-lf-rollout.md | Records HolidayLights' completed LF conversion and operational classification. |
Review effort: Lite
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #4055 +/- ##
========================================
Coverage 79.24% 79.24%
========================================
Files 38 38
Lines 12802 12802
========================================
Hits 10145 10145
Misses 2657 2657
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@coderabbitai review |
|
/review |
Action performed
|
|
Answering the round on No change needed. ptr727/HolidayLights is private, so the reviewer's token reads a 404 there. The claims were checked against a fetched clone of its
|
…ry Short Names, Stub Read Grant (#4054) ## Summary Promotes burndown round 1 of the attended run of 2026-11-10 from `develop` to `main`. - #4047: an attested local pass keeps `coverage=local` against a round that only carries a file table. A promotion now reads green Dependabot manifest bumps as covered, through the new `pr_review_promotion.py`. The promotion case also counts an attestation over direct-to-`develop` changes and excuses byte-identical renames. - #4045: the loop skills resume a parked group on a recorded answer, present each question once, accept a clone tip at or behind head, and re-check `deferred` issues whose condition is checkable. An away run's endings that cannot dispatch a promotion worker now report that. - #4046: every registry entry carries a required, gated `shortName`. A changed short name fails the spec gate as a migration. - #4044: `pull-requests: read` on each caller stub's `validate` job, the hub half of #2354. It takes effect once the lint job declares the scope. - #4052, #4053, #4055, from other sessions: registry and rollout-tracker updates. They declare Python for Vantage-Config, register the Employment repository with its short name and pin, and reconcile the HolidayLights entry. Fixes #3955 Fixes #3909 Fixes #3901 Fixes #3905 Fixes #4012 Fixes #3830 Fixes #2669 Fixes #4023 Fixes #4028 #2354 stays open for the lint job's grant and the downstream rollout. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Summary
Reconciles the hub's record of HolidayLights with what its
mainholds since ptr727/HolidayLights#17 promoted the 2025 and 2026 shows and the fleet baseline. This is the registry step of a HolidayLights resync, audit run2026-11-11T00:50:25Z | hub 1397e30a | branch override develop.registry/repos.json. Deletes thedriftNotesaying the 2025 and 2026 show folders and the baseline (ptr727/HolidayLights#11, Update branding and documentation consistency #13-Enforce squash-only merge strategy in GitHub ruleset and workflow #16) wait ondevelopfor a promotion. The audit flagged it as a note asserting pending work.docs/reusable-workflows.md. Ticks HolidayLights in both the merge-bot and thevalidate-task.ymlrows, since its callers have called each by pin since ptr727/HolidayLights#15.docs/eol-lf-rollout.md. Ticks HolidayLights as converted in ptr727/HolidayLights#10, and records its 2026-10-24 reclassification tooperational.Verification
spec/validate.pypasses, and the registry parses.origin/mainconfirms each claim: the 2021-2026 show folders, the carried instruction set, atest-pull-request.ymlcallingvalidate-task.ymlby pin, and* text=auto eol=lfwithxlights_effectpresets.jsonpinned CRLF.🤖 Generated with Claude Code
Summary by CodeRabbit