more complex release

Author: dcherian

.github/workflows/pypi-release.yaml

@@ -6,11 +6,19 @@ on:
   push:
     tags:
       - "v*"
+  pull_request:
+    types: [opened, reopened, synchronize, labeled]
+  workflow_dispatch:
 
 jobs:
   build-artifacts:
     runs-on: ubuntu-latest
-    if: github.repository == 'pydata/xarray'
+    if: ${{ github.repository == 'pydata/xarray' && (
+         (contains(github.event.pull_request.labels.*.name, 'Release') && github.event_name == 'pull_request') ||
+         github.event_name == 'release' ||
+         github.event_name == 'workflow_dispatch' ||
+         startsWith(github.ref, 'refs/tags/v')
+       ) }}
     steps:
       - uses: actions/checkout@v4
         with:

.github/workflows/test-pypi-release.yaml

@@ -48,7 +48,7 @@ upstream        https://github.com/pydata/xarray (push)
       release.
 5.  Open a PR with the release summary and whatsnew changes; in particular the
     release headline should get feedback from the team on what's important to include.
-    Apply the `Release` label to the PR to trigger a test build action, and upload to TestPyPI.
+    Apply the `Release` label to the PR to trigger a test build action.
 
 6.  After merging, again ensure your main branch is synced to upstream:
     ```sh