Create create_release.yml

[looooo]

just copying some snippets.

[looooo]

@trelau any ideas how to test the gh-action instructions?

[trelau]

@looooo no. what's the intent of this file/PR?

[looooo]

To create a release with the final sources. So we can build smesh from a zipped file.

[trelau]

To create a release with the final sources. So we can build smesh from a zipped file.

A few thoughts/questions:

• Do the final sources need to be prepared only for a release? Or should they be packaged up as an artifact for every Github Action?
• I "think" it's possible to use CMake to manage submodules and fetch external content. If retrieving the external git repos and checking out the right tag for each submodule was managed by CMake, and therefore part of the build process, would that work instead? Essentially making what's done in prepare.py part of CMake in addition to first downloading the external content.

I could imagine a few approaches:

• Modify the Github Action workflow to store as an artifact the sources (essentially the src folder after the prepare.py script is run, along with all the other supporting files of course)
• These artifacts could probably be triggered only for release builds, and I assume we could figure out how to automatically attach the artifacts to the release in Github. Otherwise, at least to start, attaching these artifacts to the release can be done manually.

[trelau]

@looooo maybe let's carry on the convo here #38? Then we can circle back on this PR convo when we have a path forward?

[looooo]

@trelau this works now on my fork. But I am not sure if uploading works as expected. Currently the upload uses the branch name, see here: https://github.com/looooo/SMESH/releases/tag/create_release

i guess this should only be done for tags / releases.

[basnijholt]

This would be quite useful, right now the smesh-feedstock relies on cloning the repo which is a very ugly solution.