[None][chore] Fix indexing conflict in blogposts#13772
Conversation
Signed-off-by: Balaram Buddharaju <[email protected]>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates image file references in a technical blog post from version 21 to version 22 assets. Four blog figure images (roofline analysis, Helix execution flow, attention sharding, and DeepSeek-R1 Pareto plot) are renumbered. No text or explanations are changed. ChangesBlog Asset References Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot skip --comment "docs update only" |
|
PR_Github #46850 [ skip ] triggered by Bot. Commit: |
|
PR_Github #46850 [ skip ] completed with state |
Signed-off-by: Balaram Buddharaju <[email protected]>
Description
There were competing MRs adding blogposts indexed at 21. This MR bumps the one that merged later to 22.
Test Coverage
N/A
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.Summary by CodeRabbit