try to attach a release

.github/workflows/go.yml

@@ -28,11 +28,42 @@ jobs:
       run: git clone https://github.com/200ok-ch/organice organice_repo
     
     - name: Build Organice
-      run: cd organice_repo && yarn install && yarn build && yarn cache clean && rm -rf node_modules && rm -rf .git
+      run: |
+      cd organice_repo
+      yarn install
+      yarn build
+      yarn cache clean
+      tar -czvf organice-${{ github.ref }}.tar.gz build
 
     - name: Copy Organice into gavin
       run: cp -r organice_repo/build organice
 
     - name: Build
-      run: gover 1.16beta1 build -v ./...
+      run: |
+      for i in openbsd darwin linux; do
+        GOOS=${i} gover 1.16beta1 build -v -o gavin-${i}
+        tar -czvf gavin-${i}.tgz gavin-${i}
+      done
+    
+    - name: Create Release
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: ${{ github.ref }}
+          release_name: Release ${{ github.ref }}
+          draft: false
+          prerelease: false
+    - name: Upload Release Asset
+        id: upload-release-asset 
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps 
+          asset_path: ./gavin-openbsd.tgz
+          asset_name: gavin-openbsd.tgz
+          asset_content_type: application/tar+gzip
+