I don't like having to download the binary build from SourceForge. And I believe a lot of open-source projects nowadays have automated CI/CD process to build the software and publish to GitHub release automatically.
So I decided to investigate whether we can implement a GitHub Actions workflow for this project. I've already finished a basic pipeline to build the exe files. Now I noticed that you have the CdiResource and License folder which is not included in the GitHub repository (maybe as intended?).
I have a solution in mind. If you would like to keep the CdiResource and License folders separate from the main source, maybe we could create a private GitHub repo and put them there. During build for release versions, a secret SSH key can be used to retrieve those files.
But before I go ahead, I would like to know your thoughts on this and also the chance of this getting merged. @hiyohiyo any feedback please?
I don't like having to download the binary build from SourceForge. And I believe a lot of open-source projects nowadays have automated CI/CD process to build the software and publish to GitHub release automatically.
So I decided to investigate whether we can implement a GitHub Actions workflow for this project. I've already finished a basic pipeline to build the exe files. Now I noticed that you have the CdiResource and License folder which is not included in the GitHub repository (maybe as intended?).
I have a solution in mind. If you would like to keep the CdiResource and License folders separate from the main source, maybe we could create a private GitHub repo and put them there. During build for release versions, a secret SSH key can be used to retrieve those files.
But before I go ahead, I would like to know your thoughts on this and also the chance of this getting merged. @hiyohiyo any feedback please?