At the moment, when a release exists wit the same tag that the one you're trying to push, you've got the choice to either fail or overwrite the release, deleting all attached asset.
This is an issue when the build process is distributed over several concurrent sessions, each responsible to upload its own set of files to a single github release.
In my case for instance, I use Travis CI to build a the same project on both linux and osx, as well as Appveyor to build on windows; each of these build being responsible to upload a platform specific binary distribution to the same GH release.
Because all these build run concurrently and it is not possible to predict which one will finish first, the required behaviour is that the first build to complete will create the release, while the other will be simply add new assets to it.
At the moment, when a release exists wit the same tag that the one you're trying to push, you've got the choice to either fail or overwrite the release, deleting all attached asset.
This is an issue when the build process is distributed over several concurrent sessions, each responsible to upload its own set of files to a single github release. In my case for instance, I use Travis CI to build a the same project on both linux and osx, as well as Appveyor to build on windows; each of these build being responsible to upload a platform specific binary distribution to the same GH release.
Because all these build run concurrently and it is not possible to predict which one will finish first, the required behaviour is that the first build to complete will create the release, while the other will be simply add new assets to it.