Sven van der Burg

I report the same issue. In fact, multiple students in my classroom with different operating systems (mac os, windows, windows) have it.

Cool, I would of course have suggested to run part of it again ;)

@sjmiller609 will this github action be triggered on pushes from **all** branches? Or **only once** upon repository instantiation.

@jlumbroso this is the same solution as @sjmiller609 proposed right? By specifying: ``` on: push: branches: - '**' ``` I tested this, and it does trigger on initialization. But it...

[Here](https://stackoverflow.com/questions/71872019/ensure-that-a-workflow-in-github-actions-is-only-ever-triggered-once) is a workaround. Basically, you disable the workflow after it has run. A fully working, but untested solution would be: ``` name: Execute workflow only upon repository initialisation on:...

I will probably have time to do this over the summer.

Submitted in: https://github.com/carpentries-lab/reviews/issues/25 🥳 I'm leaving this issue open until the review is done.

@tobyhodges I think this is solved for some alt texts with: https://github.com/carpentries-incubator/deep-learning-intro/pull/428, but that does not cover all of them right?

Great! Feel free to pick it up. And otherwise we will decide who picks it up in the next sprint!

Unfortunately, I cannot find any CC-by licensed figures that visualize this well... And I think we need a figure to explain this well. The best way would be to find...