Publish the update site on every push to main

The site only changed on a tag or a manual run, so main moved for
weeks while the site still served an August build. Publish on every
push to main, as eclipse.themes does, and skip pushes that only touch
prose or the demo. A GitHub release is still created for tags only.

Author: vogella

.github/workflows/release.yml

@@ -2,8 +2,16 @@ name: Release
 
 on:
   push:
+    branches:
+      - main
     tags:
       - 'v*'
+    # a change to the prose or the demo cannot change what p2 would serve
+    paths-ignore:
+      - '**.md'
+      - '**.adoc'
+      - 'docs/**'
+      - 'demo/**'
   workflow_dispatch:
 
 permissions:
@@ -103,7 +111,7 @@ jobs:
           git push origin gh-pages
 
       - name: Attach the repository archive to the release
-        if: github.event_name == 'push'
+        if: startsWith(github.ref, 'refs/tags/')
         env:
           GH_TOKEN: ${{ github.token }}
         run: |

Readme.adoc

@@ -13,8 +13,8 @@ The page at the same address lists the version-specific sites if you want to pin
 
 === How to release
 
-Pushing a tag that starts with `v` runs the `Release` workflow.
-It builds the p2 repository, publishes it to the `gh-pages` branch as the update site above, and attaches the repository archive to the GitHub release.
+Every push to `main` runs the `Release` workflow, which builds the p2 repository and publishes it to the `gh-pages` branch as the update site above.
+Pushing a tag that starts with `v` additionally attaches the repository archive to a GitHub release.
 
 ```bash
 git tag v1.4.0