push_to_hub_keras should support multiple models

It’s a minor UX improvement for push_to_hub_keras.

Some applications like RL or non-transformers encoder-decoder networks (CNN encoder RNN decoder) have multiple models instead of one model.

We could pass a list to model, get the model names and save those models individually under different folders and push. (check if list or a model with isinstance first)

An alternative is git pull everytime we push with push_to_hub_keras (which is cumbersome in a notebook) and call push_to_hub_keras repeatedly for every model.

cc: @osanseviero

[osanseviero]

I feel only the following sections are needed:

1. Model desc (for full thing)
2. Intended uses and limitations
3. Training and eval data
4. Train procedure for model A
5. Model Plot for model A
6. Training procedure for model B
7. Model Plot for model B

Maybe before 4, we can have a section saying “this repository consists of X models”. Then before 4 and before 6, have a heading with “Further information for model A|B”. WDYT? We could do this by breaking the readme function a bit I feel.

[nateraw]

Sure, I like this idea 😄 . Would be very helpful especially in the case of GANs. I’d really be curious to know if other folks want this feature.

As for model card, I think we can either do what @osanseviero is describing, or just leave it as-is. I’m guessing this would only be used when models are trained together. People probably shouldn’t be dumping unrelated models in the same repo and we don’t want to encourage that.