Conversation
|
Hi, I have ported your work to GitHub Actions: https://github.com/mcejp/wxHexEditor/tree/feature/CI-AppImage It doesn't push a GitHub release though, just an artifact. |
|
Hello. Thanks for your work. |
|
@EUA maybe a good way would be to build the AppImage for each build (it can be helpful for developers and testers) but not upload it to GitHub Releases (only to GitHub Artefacts)? |
|
@probonopd Yup. I will try to make AppImage when I make release. But first I need to learn how to do it. |
|
At this time I'd really recommend to use GitHub Actions instead of Travis CI. Would you be interested in a pull request that does it? |
This PR, when merged, will compile this application on Travis CI upon each
git push, and upload an AppImage to your GitHub Releases page.Providing an AppImage would have, among others, these advantages:
appimaged--appimage-extractparameterHere is an overview of projects that are already distributing upstream-provided, official AppImages.
PLEASE NOTE: For this to work, you need to set up
GITHUB_TOKENin Travis CI for this to work; please see https://github.com/probonopd/uploadtool.If you have questions, AppImage developers are on #AppImage on irc.freenode.net.