With this approach, the release is published immediately and the files are attached later-assuming the action is executed successfully. So far we pushed a tag and then manually created a release via the GitHub website. It should now have the packaged application for all platforms attached. In the "Actions" tab we can now see that our newly created workflow is executed.Īfter it has finished, we go back to our release ( example). As "Tag version" we chose "v1.0.0" and click "Publish release". It also accesses the GITHUB_TOKEN and is only executed for created releases.Īfter pushing all changes, we can go to the "Releases" section in the "Code" tab of the repository and click "Create a new release". It is basically the same as build.yaml but uses the publish script ( make is not needed, this would build the app twice). We need to install it in our example project. That's exactly what we need.Įlectron Forge provides a GitHub publisher that does all the work for us. changelog) and can have files attached to it. For that, we want to utilize GitHub releases.Ī release is based on a Git tag. While this is useful for developers, it is not sufficient for providing the application to users. That's it! 🚀 We are now building a native application on Windows, Linux and macOS.įine, now how do we get access to the distributable files? We could set up artifact uploading for this. Click on it to see the individual tasks and wait for them to finish. We can see our newly created workflow running. The workflow is executed for all branches and for pull requests to verify that the application can still be built after making changes.Īfter pushing the file, we go to the "Actions" tab of the repository ( example). It basically defines the same job three times for different operating systems. Enter fullscreen mode Exit fullscreen mode
0 kommentar(er)
