Included workflows are not tested on CI

[krassowski]

Time (#221) and again (jupyter-server/jupyter_releaser#474) and again (#258) the CI workflows generated by cookiecutter turn out to be broken. This is not a good experience for new extension authors, and not a good experience for established developers either.

The question is how to run generated workflows in CI without them being in root .github/workflows.

Two options that I see

• use https://github.com/nektos/act to execute workflows directly
• create a branch with the new content, wait for CI on the branch to finish (basically creating a custom service that interfaces between branches/repositories)
  • might be problematic permission-wise

[blink1073]

Another option is to put the business logic in shell scripts, and then execute those directly, as we do in the server cookiecutter

[bollwyvl]

+1 to the shortest possible scripts I've can also run locally. Python can be less alien than shell, and more portable.