Separation Releases

[mikoloism]

To split CONTINUOUS DEPLOYMENT GitHub Actions for each Target Architecture.

Benefits can be imagined:

• avoiding side effects
• no fail another platforms build if single one make fails
• improving easy maintainability
• improving fast modularity releases*

*: can be easily add/delete action file

Cons can be imagined:

• increase repository size
• more boilerplates

For more information, there is discussion in GitHub Community also available

Note

Inspired from issue in #695 (comment)

[mikoloism]

After deliberation and final decision, I volunteer to do the separation

[mikoloism]

Hi dear @sayanarijit

To make this option possible, we need to attach additional binary asset files to GitHub release page from git tags.

In our actions we are using action-gh-releases... but after reading documentation of it, it's not support to attach from multiple GitHub Action files to single releases.
To make it possible, I recommended to switch to upload-release-assets.

what features not compatible of upload-release-assets to action-gh-releases?

If you think it's not good enough to use for the project, you can let me know so I can avoid further change.

[sayanarijit]

Sounds good 👍