[ci] trigger workflow

.github/workflows/release.yml

@@ -1,7 +1,8 @@
 name: Publishing Release
 on:
+  pull_request:
+    types: [opened, synchronize, reopened]
   release:
-    # https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#release
     types: [published]
 
 jobs:
@@ -42,25 +43,31 @@ jobs:
           export CXX=clang++
           python misc/ci_setup.py ci
 
-      - name: Test
+      - name: Build Python Wheel
         run: |
           export TAICHI_REPO_DIR=`pwd`
           export PATH=$TAICHI_REPO_DIR/bin:$PATH
           export PATH=$TAICHI_REPO_DIR/taichi-llvm/bin/:$PATH
           export PYTHONPATH=$TAICHI_REPO_DIR/python
-          python examples/laplace.py
-          ti diagnose
-          ti test -vr2 -t2
+          cd python
+          python build.py build
+
+      - name: Archive Wheel Artifacts
+        uses: actions/upload-artifact@v2
+        with:
+          # While ${{ github.ref }} does provide the release tag, it is of
+          # format `refs/tags/<tag_name>`, which isn't a valid file path.
+          name: taichi-py${{ matrix.python }}-${{ matrix.os }}.whl
+          path: python/dist/*.whl
 
       # TODO(#1580): Upload to PyPI. Need to set up PYPI_PWD in the secrets first.
-      - name: Upload PyPI
+      - name: Fake PyPI Upload
         env:
-          # https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow
-          PYPI_PWD: ${{ secrets.PYPI_PWD }}
+          PYPI_PWD: "fakefakefake"
         run: |
           export TAICHI_REPO_DIR=`pwd`
           export PATH=$TAICHI_REPO_DIR/bin:$PATH
           export PATH=$TAICHI_REPO_DIR/taichi-llvm/bin/:$PATH
           export PYTHONPATH=$TAICHI_REPO_DIR/python
           cd python
-          python build.py try_upload && bash <(curl -s https://codecov.io/bash)
+          python build.py try_upload --skip_build

python/LICENSE.txt

@@ -12,6 +12,7 @@ furnished to do so, subject to the following conditions:
 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.
 
+
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE