feat: group migrate GGUFs with adopt-or-edit and hub family reuse - #23
Merged
Conversation
Quant clusters pick as one group; TTY can adopt the set or edit files first, then family once from names already in the hub.
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
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
--yes/--jsonstill take whole groups with no extra prompts. Singletons keep id + family.Test plan
mba migrate find llama— pick a multi-file cluster, confirm the preview lists files, adopt the whole group, family once, quiet bulkADOPTEDrowsmba models search/ TTYmba models pull … --id …(no--family) offers existing hub families + new--yes/--jsonskip adopt/edit and take whole groupsMade with Cursor