video shared here: https://www.kubeflow.org/docs/started/getting-started-gke/
A suggestion would be to write down the commands applied below the video.
Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.53. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
/assign @texasmichelle
@texasmichelle This is an interesting point, which will apply to all videos. The videos need to provide enough tech info for people to be able to follow up on them. Even just a doc link would be good enough, I think.
The sentence directly in front of the video includes a link to all the commands used ("All code used in this video can be found in the examples repository"). If this is what you're looking for, is there clearer language we could use to make that more obvious or prominent?
@texasmichelle , you are correct. Sorry, I opened directly the kubeflow examples repository when you mentioned them at the video, and later I thought that link ("examples repository") would direct me here to main https://github.com/kubeflow/examples
Thanks a lot for all your great work, I'm learning a lot.