Replies: 6 comments 1 reply
-
Actually, this can be automated with Github actions based on the commit message. |
Beta Was this translation helpful? Give feedback.
-
another option is |
Beta Was this translation helpful? Give feedback.
-
Still not the same as just downloading the binaries which is the standard everywhere. |
Beta Was this translation helpful? Give feedback.
-
Binaries without corresponding headers are barely useful. |
Beta Was this translation helpful? Give feedback.
-
I meant the executables. But you could also pack the headers in a tar.gz/zip file and upload that along with everything else. |
Beta Was this translation helpful? Give feedback.
-
documentation + headers + executables are pretty much all what changes. So it is not clear what shall be put in that zip file and how it shall be different from https://github.com/c-smile/sciter-js-sdk/archive/refs/heads/main.zip |
Beta Was this translation helpful? Give feedback.
-
Since sciter-js is already on GitHub, it would be amazing if the binaries were uploaded to GitHub Releases for easier downloading & trying. Currently, the only way to download Sciter is to clone the whole repo which is in GBs and includes a lot of unnecessary stuff. The second option is to use a GitHub folder downloading tool — even then you are left with a lot of frustration.
It would be really helpful for developers if releases were versioned along with their changelogs like you are already doing in the logfile.
Beta Was this translation helpful? Give feedback.
All reactions