Repository navigation
Conform CHANGELOG.md entries to the house style - #20
Conversation
Format-only pass: rewrite nonconforming bullets to one-line house-style form. No changes added, removed, moved, or re-versioned. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟡 Changes recommended
A couple of rewritten bullets become ambiguous or lose key meaning compared to the original entries, reducing the changelog’s clarity.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Reformats CHANGELOG.md entries to match the project’s house style by condensing verbose bullets into shorter, consistent, sentence-style entries while keeping the existing version/section structure intact.
Changes:
- Condense the Unreleased “Changed” section into short bullets and sub-bullets.
- Shorten and normalize a few 0.8.2 / 0.8.1 “Changed” bullets to match the standard style.
File summaries
| File | Description |
|---|---|
| CHANGELOG.md | Condenses and normalizes changelog bullets to the house style without restructuring versions/sections. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - Update the dataset page and the Data Science FAQ. | ||
| - Move the 2022 FAQ, the 2024 CS2 pages, and the CS:GO pages under `datascience/old/`. | ||
| - Harden the deploy workflows. | ||
| - Update GitHub Actions to Node 24 runtimes. |
There was a problem hiding this comment.
Addressed by the fleet-wide rename to "Update GitHub Actions to Node.js 24 runtimes." - the line names the Actions runtimes, not the toolchain Node version.
Restore lost operational notes (fail-open captcha, DLQ watch, staging deploy target, stage qualifier, deferred non-pro matches), fix an ambiguous LSI bullet and two grammar issues, tighten blank lines between bullets, and say Node.js 24 for the Actions runtimes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
🔵 Needs a closer look
There’s a small remaining style inconsistency (gh-pages not formatted as a literal identifier) in an otherwise style-focused changelog conformance PR.
Review details
Suppressed comments (1)
Previously missed (1) — in code that hasn't changed since the last review.
CHANGELOG.md:34
- To match the surrounding convention of marking code/identifier-like names in backticks (e.g.,
npm publish),gh-pagesshould be formatted as a literal identifier here as well.
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Lite
Say one poll per 5 s instead of 1/5s, name the environment=staging input on the release.yml deploy note, and backtick the gh-pages job. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
On the suppressed gh-pages note: fixed in the follow-up commit - |
There was a problem hiding this comment.
🟢 Approval recommended
The changes are limited to changelog wording/formatting and appear to preserve the existing structure and meaning without introducing inconsistencies.
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Lite
What
Rewrites every nonconforming
CHANGELOG.mdbullet in the house style: one bullet per change, a fragment or one short sentence with a full stop, named the way the pre-2026 entries name things.Part of the fleet-wide conformance pass. The style itself is codified in the
igl-*CLAUDE.md PRs (igl-gotv #49); recent entries had drifted into multi-paragraph essays with measured figures and design rationale.Invariants
CHANGELOG.mdchanges; the##version-heading sequence is byte-identical, and no entry moved between versions or sections.Requires ...deploy-order notes survive as the permitted second sentence; breaking markers are normalized to(**Breaking**).🤖 Generated with Claude Code