[https://nvbugs/6109719][doc] Remove outdated items in previous news sections.#13603
Conversation
|
/bot run |
📝 WalkthroughWalkthroughThe README.md file was updated to remove a dated news item from June 17 about a NVIDIA and DeepInfra developer meetup. Markdown list formatting was adjusted by adding blank-line separators around remaining news entries. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Around line 88-96: Replace the generic "➡️ link" alt text with descriptive
link text for the news bullets so they meet MD059; update the three affected
list items referencing "GPT-OSS-120B / GPT-OSS-20B" (08/05), "EXAONE 4.0"
(07/15), and "Blackwell Breaks the 1,000 TPS/User Barrier With Meta’s Llama 4
Maverick" (05/22) to use meaningful anchor text (e.g., "GPT-OSS-120B on Hugging
Face", "EXAONE 4.0 on Hugging Face", "NVIDIA blog: Blackwell breaks 1,000
TPS/User barrier") while keeping the same URLs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 0efe2fdb-0041-4fa9-9ac3-0845e1189819
📒 Files selected for processing (1)
README.md
nv-guomingz
changed the title
|
PR_Github #46093 [ run ] triggered by Bot. Commit: |
|
PR_Github #46093 [ run ] completed with state
|
|
/bot run |
|
PR_Github #46132 [ run ] triggered by Bot. Commit: |
|
PR_Github #46132 [ run ] completed with state
|
nv-guomingz
force-pushed
the
user/guomingz/fix_nvbug_6109719
branch
from
17f7eea to
564e911
Compare
|
/bot run |
|
PR_Github #46142 [ run ] triggered by Bot. Commit: |
|
PR_Github #46142 [ run ] completed with state
|
Signed-off-by: nv-guomingz <[email protected]>
nv-guomingz
force-pushed
the
user/guomingz/fix_nvbug_6109719
branch
from
564e911 to
23dec9d
Compare
|
/bot run |
|
PR_Github #46186 [ run ] triggered by Bot. Commit: |
|
PR_Github #46186 [ run ] completed with state |
…sections. (NVIDIA#13603) Signed-off-by: nv-guomingz <[email protected]>
…sections. (NVIDIA#13603) Signed-off-by: nv-guomingz <[email protected]>
3 participants
Summary by CodeRabbit
Description
Test Coverage
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.