Target branch/tag/commit for automatic Hub pushes

🤗Transformers
1

I’m looking to contribute a feature allowing users to specify a target revision (branch, tag, or commit hash) for automatic Hub pushes during training.

Currently, when using Trainer with push_to_hub=True and strategies like hub_strategy="checkpoint", automatic pushes always go to the default branch. While manual calls to push_to_hub() support specifying a revision, automatic pushes don’t seem to offer this option.

I’d like to introduce a hub_revision parameter in TrainingArguments, enabling users to specify the revision used for automatic uploads. This would apply to all Hub uploads, including checkpoints saved during training. For instance, instead of creating new repositories or overwriting the main branch, users could push checkpoints to a dedicated branch like experiment-123.

I’ve prepared a draft implementation here: [WIP] Add support for specifying revisions when pushing to Hub via internal Trainer call by IsaacBreen · Pull Request #36852 · huggingface/transformers · GitHub. Before finalizing it, I wanted to confirm there’s no existing solution that I’ve overlooked.

1 Like
2

Setting the right target branch or commit is crucial for smooth Hub pushes especially when working with llamacpp integrations. It really helps avoid unexpected deployment issues.

1 Like