docs: List all trainers that support Liger Kernel #4432
Merged
+59
−10
Conversation
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
Resolves #4386 - Add "Supported Trainers" section listing SFT, DPO, GRPO, KTO, and GKD - Replace single SFT example with hfoptions showing all 5 supported trainers - Remove "under construction" warning as guide is now complete - Follow same format as reducing_memory_usage.md for consistency
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Improves the Liger Kernel integration guide by clearly listing all supported trainers and providing examples for each.
Resolves #4386
Changes
File Modified:
docs/source/liger_kernel_integration.mdImprovements:
Added "Supported Trainers" section listing all 5 trainers that support Liger:
Enhanced examples with hfoptions tabs showing usage for all 5 trainers instead of just SFT
Removed "under construction" warning as the guide is now comprehensive
Improved consistency by following the same format as
reducing_memory_usage.mdVerification
use_liger_kernelimplementationBefore this PR, only SFT was shown as an example, making it unclear which other trainers support Liger. Now users can easily see all supported trainers and find the example for their specific use case.