-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update hfh #700
Update hfh #700
Conversation
Maybe we will want to change this later once huggingface/huggingface_hub#1288 is fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! :)
Out of curiosity, how to you get the source_revision
(which I guess is the initial commit) ? We have a user that wants to retrieve this information programmatically but for now we don't have a endpoint for that so I'd be interested if a workaround exists for it :)
Oh, for now, it's hard-coded to And it's not really useful to create the branch from main or from any other commit, since the first action is to delete all the contents, before adding the files we are interested in (parquet files). The |
Oh ok, makes sense. I thought you had a trick to know the initial commit. |
Yes, that's what I mentioned in the commit message: 5364f81
|
if you just want an empty tree (and not the initial commit of the repo), you can also create a commit completely detached from any branch (i think we discussed this in the other issue but i don't remember the discusion) |
Could be a solution but not implemented via the HTTP endpoint so far. |
(yes, but you could re-add a "standard" gitattributes quite easily in your commit i guess) |
(i do agree with you, this is just for the sake of discussion) |
In particular: we now use the new
list_repo_refs
method, and the newrevision
parameter when we create therefs/convert/parquet
branch.