# TRAVIS CI and GitHub

**URL:** <https://travis-ci.community/t/travis-ci-and-github/9126>\
**Category:** Deployment\
**Tags:** github-integration, travis-build, github-releases\
**Created:** [June 25, 2020, 5:03am UTC](https://travis-ci.community/t/travis-ci-and-github/9126 "2020-06-25T05:03:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Portree-Kid](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/portree-kid/32/4842_2.png) [@Portree-Kid](https://travis-ci.community/u/Portree-Kid)\
**Post date:** [June 25, 2020, 5:03am UTC](https://travis-ci.community/t/travis-ci-and-github/9126/1 "2020-06-25T05:03:27Z")

</div>

**Travis Splits Release**  
I have a cross plattform build of an electron app. The build runs fine, but I can’t get it to make a combined release. Windows will always be in a separate Github-Release. This also means a clash of tags if I generate a tag. That’s the reason it is an untagged build. Any examples for this?  
[FG Airports](https://travis-ci.org/github/Portree-Kid/flightgear-airports)

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [June 25, 2020, 12:39pm UTC](https://travis-ci.community/t/travis-ci-and-github/9126/2 "2020-06-25T12:39:38Z")

</div>

Combine

> **[Travis CI Documentation](https://docs.travis-ci.com/user/using-workspaces)**
>
> Using Workspaces (Beta)

  
and  

> **[Travis CI Documentation](https://docs.travis-ci.com/user/build-stages)**
>
> Build Stages

  
so that your OS jobs will create build artifacts and the deploy stage job collects these artifacts to create a release.