fix example yaml - #709
Merged
Merged
Conversation
add detail comment for nvidia specify card case. Signed-off-by: lixd <xueduan.li@gmail.com>
Shouren
reviewed
Dec 16, 2024
Signed-off-by: lixd <xueduan.li@gmail.com>
Shouren
reviewed
Dec 16, 2024
Signed-off-by: lixd <xueduan.li@gmail.com>
Contributor
Author
|
@archlitchi have a look |
Member
|
/lgtm |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Flags with carried forward coverage won't be shown. Click here to find out more. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
add detail comment for nvidia specify card case.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
add detail comment to nvidia specify card case to be more user-friendly. avoid wrong use，like #707
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: