Automated testing episode contains too many steps

[bast]

There is risk that we lose focus on what this really is about.

[bast]

Ran out of time but summarizing here what I think should be done:

• we should focus here on the essence: automated testing, coupling it to PRs
• provide a repo with a simple code
• let learners generate/fork from it
• let them add a workflow file
• observe that actions pick it up
• create a branch on the web
• fix an issue
• create PR
• observe how it turns to green

All the other distraction should be removed. There is way too much and it distracts from what this is really about.

[jpthiele]

What is the progress here?
I'd be happy to setup and include examples and repositories for Julia and C++
but if you still plan on cutting down the episode that might be a lot of unnecessary work
for everyone.

[bast]

I still think it's too many steps and this has not been reduced. I hope that for the upcoming September workshop we go through the open issues when preparing.