First commit after migrating from gitlab to github

I decided to try github out instead of my old gitlab repo
(https://gitlab.com/maltfield/cross-platform-python-gui/) because it has
native support for building on MacOS using free GitHub-hosted runners

 * https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on

This is the first time I've setup a CI workflow on GitHub, so it may
take a few commits for this migration to actually produce successful
builds..

Author: maltfield

.github/workflows/build.yml

@@ -0,0 +1,43 @@
+name: build
+
+# execute this workflow automatically, but only when pushing to master
+on:
+  push:
+    branches: [ master ]
+#  pull_request:
+#    branches: [ master ]
+
+jobs:
+
+  linux:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: docker://debian:buster-slim
+    - uses: actions/checkout@v2
+
+    - name: Execute script to build linux AppImage
+      run: "build/linux/buildAppImage.sh"
+      shell: bash
+
+    - uses: actions/upload-artifact@v2
+      with:
+        name: Linux AppImage (x86_64)
+        path: dist/
+
+  windows:
+    runs-on: windows-latest
+
+    steps:
+    - uses: docker://debian:buster-slim
+    - uses: actions/checkout@v2
+
+    - name: Execute script to build linux AppImage
+      run: "build/windows/buildExe.ps1"
+      shell: powershell
+
+    - uses: actions/upload-artifact@v2
+      with:
+        name: Windows executable (x86_64)
+        path: dist/
+

.gitlab-ci.yml

@@ -1,4 +1,4 @@
-[![pipeline status](https://gitlab.com/maltfield/cross-platform-python-gui/badges/master/pipeline.svg)](https://gitlab.com/maltfield/cross-platform-python-gui/-/commits/master)
+![](https://github.com/maltfield/cross-platform-python-gui/workflows/build/badge.svg)
 
 # Cross Platform Python GUI
 
@@ -11,13 +11,13 @@ It includes the CI pipeline to automatically build self-contained executables fo
 1. Fork this repo
 2. Edit [src/main.py](/src/main.py) as needed
 3. Add any required python modules to [requirements.txt](/requirements.txt)
-4. Go to Settings -> CI/CD and make sure that you have defined a "General pipeline." The default settings should be fine.
 
-When you push git commits to gitlab on master, gitlab will automatically spin up containers in GCP and build your application's executables for all target platforms.
+When you push git commits to github on master, github will automatically spin up containers in the cloud and build your application's executables for all target platforms.
 
 # TODO
 
-1. Figure out how to build a Mac release on gitlab shared runners in GCP (vagrant with libvirt?)
+1. Finish migration from gitlab to github (get workflows working for linux & mac builds)
+2. Add CI workflow for building MacOS binaries
 
 # License