Skip to content

[1/2] docs: date-prefix announcement filenames - #2917

Merged
kevalmorabia97 merged 3 commits into
mainfrom
kmorabia/announcements-date-prefix
Oct 21, 2026
Merged

kevalmorabia97 merged 3 commits into
mainfrom
kmorabia/announcements-date-prefix

Conversation

@kevalmorabia97

@kevalmorabia97 kevalmorabia97 commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

What does this PR do?

Type of change: documentation

Renames every announcement page to <yyyymmdd>-<slug>.rst, using its publication date, so the pages sort by date in the source tree. The index cards and the README blog links point to the new paths. The GitHub Pages announcement's authoring note states the convention.

The old URLs keep working: docs/source/conf.py enables sphinxext-rediraffe (MIT, added to the dev-docs group; uv.lock is left to the weekly bump) and maps each old page to its dated one in rediraffe_redirects. Rediraffe writes a redirect page at every old path that keeps the query and #fragment, and warns (so the --fail-on-warning docs build fails) when a target page does not exist.

Merge order: this is [1/2]; #2915 (GLM-5.3-Flash announcement) is stacked on it.

Usage

N/A (documentation)

Testing

  • git grep for the old announcement paths: no references left in the repo.
  • Clean HTML build (sphinx 9.1, sphinxext-rediraffe 0.3.0, nemo:26.08 container): all 8 dated pages and all 8 redirect pages are written, every index card link resolves, and no warning mentions the announcements, redirects or conf.py. The build had unrelated autodoc warnings from that environment, so it was not run with --fail-on-warning; CI's docs job does that.
  • Added a redirect to a page that does not exist: rediraffe reports it as broken with a warning.

Before your PR is "Ready for review"

  • Is this change backward compatible?: ✅ Old announcement URLs redirect to the new pages.
  • If you copied code from any other sources or added a new PIP dependency, did you follow guidance in CONTRIBUTING.md: ✅ sphinxext-rediraffe is MIT licensed (docs-only dependency).
  • Did you write any new necessary tests?: N/A
  • Did you update Changelog?: N/A
  • Did you get Claude approval on this PR?: ❌

Additional Information

#2899 edits qwen36-w4a4-qad.rst under its old name; git's rename detection should carry the change over, but whichever merges second may need a rebase.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated announcement links to use date-prefixed URLs for improved chronological navigation.
    • Added guidance requiring announcement pages to follow the date-based filename format.
    • Updated the latest news links to reference the new announcement URLs.
  • Bug Fixes
    • Added redirects from legacy announcement URLs so existing bookmarks and links continue to work.

Name announcement pages <yyyymmdd>-<slug>.rst so they sort by date, and point the
index cards and README links at the new paths.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Keval Morabia <28916987+kevalmorabia97@users.noreply.github.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 21, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: NVIDIA/Model-Optimizer/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 7246364f-0fe7-44c5-88cf-f568eb81ddd1
📥 Commits

Reviewing files that changed from the base of the PR and between 5e47e2b and 7af729f.

📒 Files selected for processing: 2
  • docs/source/conf.py
  • pyproject.toml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 9 remain after this review.

📝 Walkthrough

Announcement authoring instructions and links now use date-prefixed paths. Sphinx enables sphinxext.rediraffe and maps legacy announcement paths to dated paths.

Changes: Announcement paths and redirects

Layer / File(s) Summary
Document dated announcement paths
docs/source/announcements/20260813-github-pages-announcements.rst, docs/source/index.rst, README.md
The authoring instructions specify the <yyyymmdd>-<slug>.rst filename format. Announcement links use date-prefixed paths.
Configure announcement redirects
pyproject.toml, docs/source/conf.py
The documentation dependencies include sphinxext-rediraffe. Sphinx enables the extension and maps eight legacy announcement paths to date-prefixed paths.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related issues

  • NVIDIA/cuda-quantum#5386 — This PR adds redirects for renamed announcement pages, which aligns with the issue’s objective of preserving old documentation URLs after content moves.

Suggested reviewers: shengliangxu, cjluo-nv

Merge Risk: ⚪ Minimal · up to 7af72

The dated announcement links and legacy redirects are consistent. No issue identified here needs to be resolved before merging.

Pre-merge checks: Passed 6
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely identifies the primary change: adding date prefixes to announcement filenames.
Docstring Coverage Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files. (1 skipped: 1 …
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Security Anti-Patterns Passed The pull request changes documentation configuration, announcement filenames, links, and one optional documentation dependency. It introduces no changes under modelopt/ or examples/ Python files, …
Full details: Docstring Coverage

Explanation

Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files. (1 skipped: 1 unsupported.)

Full details: Security Anti-Patterns

Explanation

The pull request changes documentation configuration, announcement filenames, links, and one optional documentation dependency. It introduces no changes under modelopt/ or examples/ Python files, and therefore introduces none of the listed Python security anti-patterns. The added sphinxext-rediraffe dependency is identified in the PR description as MIT licensed, which is permissive under this check.

✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@kevalmorabia97

Copy link
Copy Markdown
Collaborator Author

/ok to test c02883d

@kevalmorabia97
kevalmorabia97 marked this pull request as ready for review October 21, 2026 17:23
@kevalmorabia97
kevalmorabia97 requested review from a team as code owners October 21, 2026 17:23

@cjluo-nv cjluo-nv left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bot review (gpt-6.1-sol) — DM the bot to share feedback.

Changes requested: the filename-only cleanup breaks all eight existing public announcement URLs without redirects.

Needs action:

  • Preserve the old announcement URLs with redirects or compatibility pages pointing to the dated URLs; see the inline comment in docs/source/index.rst.
  • Run a clean Sphinx HTML build and verify that all eight dated pages, index links, and legacy redirects resolve; record the results in the PR description.

Comment thread docs/source/index.rst
@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-21 18:31 UTC

@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.91%. Comparing base (6d76b59) to head (7af729f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2917      +/-   ##
==========================================
+ Coverage   70.16%   78.91%   +8.75%     
==========================================
  Files         659      659              
  Lines       74081    74081              
==========================================
+ Hits        51978    58463    +6485     
+ Misses      22103    15618    -6485     
Flag Coverage Δ
examples-diffusers 20.04% <ø> (-0.01%) ⬇️
examples-gpt-oss 13.51% <ø> (-0.01%) ⬇️
examples-hf_ptq 23.19% <ø> (-0.04%) ⬇️
examples-llm_distill 13.59% <ø> (-0.01%) ⬇️
examples-llm_eval 17.24% <ø> (+<0.01%) ⬆️
examples-llm_qat 17.48% <ø> (-0.01%) ⬇️
examples-llm_sparsity 15.76% <ø> (-0.01%) ⬇️
examples-megatron_bridge 26.43% <ø> (-0.13%) ⬇️
examples-specdec_bench 13.29% <ø> (-0.01%) ⬇️
examples-speculative_decoding 17.47% <ø> (-0.01%) ⬇️
examples-torch_onnx 21.39% <ø> (-0.01%) ⬇️
examples-torch_trt 15.24% <ø> (-0.01%) ⬇️
examples-vllm_serve 15.08% <ø> (-0.01%) ⬇️
gpu 59.18% <ø> (+37.05%) ⬆️
regression 15.10% <ø> (-0.01%) ⬇️
unit 60.60% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Keval Morabia <28916987+kevalmorabia97@users.noreply.github.com>
@kevalmorabia97

Copy link
Copy Markdown
Collaborator Author

/ok to test 5e47e2b

Replace the custom build-finished hook with the MIT-licensed rediraffe
extension, which writes the same redirect pages and warns on missing targets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Keval Morabia <28916987+kevalmorabia97@users.noreply.github.com>
@kevalmorabia97
kevalmorabia97 requested a review from a team as a code owner October 21, 2026 17:51
@kevalmorabia97

Copy link
Copy Markdown
Collaborator Author

/ok to test 7af729f

@cjluo-nv cjluo-nv left a comment •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bot review (gpt-6.1-sol) — DM the bot to share feedback.

LGTM: the prior URL-compatibility and build-validation concerns are resolved; human sign-off remains for the new MIT-licensed documentation dependency.

Needs action:

  • Confirm licensing approval for sphinxext-rediraffe in pyproject.toml before merging.

No action needed:

  • ✔️ Resolved since the last review: all eight legacy paths have redirect mappings, and clean-build/link-validation results are recorded in the PR description.
  • The dated filenames, redirect targets, index cards, and README links agree. CI installs dev-docs and builds with --fail-on-warning; leaving uv.lock unchanged follows CONTRIBUTING.md.
  • Build results were reviewed as reported; I did not execute Sphinx locally.

@kevalmorabia97
kevalmorabia97 enabled auto-merge (squash) October 21, 2026 17:55
@kevalmorabia97
kevalmorabia97 merged commit 31e9ea6 into main Oct 21, 2026
58 checks passed
@kevalmorabia97
kevalmorabia97 deleted the kmorabia/announcements-date-prefix branch October 21, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants