Have permanent repos on the hub representing the results of our examples

[adrinjalali]

Our examples in docs push to temporary repos, which means we can't have a link at the end to refer users to the generated repositories.

We can't push to permanent ones from the docs since we have our keys exposed there, so we should have more like a cron job which pushes to a permanent repo.

We probably need one repo for each version of the package, and have a way to link to those repositories from the docs.

For example, it would be nice to have the result of our model card example to be somewhere on the hub.

@merveenoyan you might be interested in this.

[ketangangal]

can i take this issue ?

[BenjaminBossan]

@ketangangal It's certainly possible, though depending on the solution, it might require some support from us maintainers (like adding secrets to the repo). What would be your approach to tackle this?

[merveenoyan]

This is already done no? I did it at least for our kaggle examples.
For the rest, maybe we could write a GHAction to automate it.

[ketangangal]

Please @merveenoyan let me know, If i can do something ! I am new to open-source want to make some contribution to skops.

[adrinjalali]

I don't think it's done. We have examples which we manually have created on the hub, and they're not updated when we update examples on the repo and our docs.

This is not an easy task or a good first issue. This is about pushing the results of the examples we have to the hub, and have a link to the repo on the documentation under the examples. It involves a bit of work.

[merveenoyan]

@adrinjalali I think I can try and write a GH Action, open a repository and push and then we can clean up we can push. WDYT?

[adrinjalali]

@merveenoyan that sounds like the right approach to me.