Restricting github-Workflows in forked repos which include pushing an image to DockerHub about force HOT 5 CLOSED

Thanks @Florian-Katerndahl,

yes, this makes much sense. But doesn't the same issue apply to the other workflows, too?

Cheers,
David

from force.

Hey David,
there's only one other workflow, no? Although under "actions" there is indeed a fourth one which I never encountered.
The Docker-test Workflow only runs on Github's infrastructure. Because of this, there is no error - nothing's getting pushed to a remote place.

While it doesn't concern me at the moment, the docker-test-workflow could be seen as a quick check if something major broke during development. Though, I don't know if this approach/thought makes sense.

from force.

Ah, in your first message it says "docker-publish-debug.yml" and "docker-debug.yml". This confused me, I assume that the latter should be "docker-publish.yml", right?

Yes, for the Docker test, it makes sense that this runs for everybody.
Under "Actions", there is another one ("Compile"), which is not existing anymore.
This was deprecated and substituted with the Docker Test.

Feel free to PR. I like that addition!

from force.

Yes, you're right, I meant to "docker-publish.yml".

from force.

@davidfrantz This is included in #130

from force.