handle config_name=None in push_to_hub
MEMBER
not sure it's a good idea, we always need a config name so better have the correct default and not support None (which could lead to think it doesn't have a config name, while it does)
2024-10-24T15:08:53Z
https://github.com/huggingface/datasets/pull/7229#issuecomment-2435563608
https://api.github.com/repos/huggingface/datasets/issues/7229
IC_kwDODunzps6RK8BY
https://api.github.com/repos/huggingface/datasets/issues/comments/2435563608/reactions
2024-10-24T15:08:53Z
https://api.github.com/repos/huggingface/datasets/issues/comments/2435563608
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
This caught me out - thought it might be better to explicitly handle None?